CVE Vulnerabilities

CVE-2023-49125

Out-of-bounds Read

Published: Feb 13, 2024 | Modified: Oct 18, 2024
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

A vulnerability has been identified in Parasolid V35.0 (All versions < V35.0.263), Parasolid V35.1 (All versions < V35.1.252), Parasolid V36.0 (All versions < V36.0.198), Solid Edge SE2023 (All versions < V223.0 Update 11), Solid Edge SE2024 (All versions < V224.0 Update 3). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted files containing XT format. This could allow an attacker to execute code in the context of the current process.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Parasolid Siemens 35.0 (including) 35.0.263 (excluding)
Parasolid Siemens 35.1 (including) 35.1.252 (excluding)
Parasolid Siemens 36.0 (including) 36.0.198 (excluding)
Solid_edge_se2023 Siemens * 223.0 (excluding)
Solid_edge_se2023 Siemens 223.0-update_0001 (including) 223.0-update_0001 (including)
Solid_edge_se2023 Siemens 223.0-update_0002 (including) 223.0-update_0002 (including)
Solid_edge_se2023 Siemens 223.0-update_0003 (including) 223.0-update_0003 (including)
Solid_edge_se2023 Siemens 223.0-update_0004 (including) 223.0-update_0004 (including)
Solid_edge_se2023 Siemens 223.0-update_0005 (including) 223.0-update_0005 (including)
Solid_edge_se2023 Siemens 223.0-update_0006 (including) 223.0-update_0006 (including)
Solid_edge_se2023 Siemens 223.0-update_0007 (including) 223.0-update_0007 (including)
Solid_edge_se2023 Siemens 223.0-update_0008 (including) 223.0-update_0008 (including)
Solid_edge_se2023 Siemens 223.0-update_0009 (including) 223.0-update_0009 (including)
Solid_edge_se2023 Siemens 223.0-update_0010 (including) 223.0-update_0010 (including)
Solid_edge_se2024 Siemens * 224.0 (excluding)
Solid_edge_se2024 Siemens 224.0-update_0001 (including) 224.0-update_0001 (including)
Solid_edge_se2024 Siemens 224.0-update_0002 (including) 224.0-update_0002 (including)

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References