CVE Vulnerabilities

CVE-2022-33884

Out-of-bounds Read

Published: Oct 03, 2022 | Modified: Oct 07, 2022
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Parsing a maliciously crafted X_B file can force Autodesk AutoCAD 2023 and 2022 to read beyond allocated boundaries. This vulnerability in conjunction with other vulnerabilities could lead to code execution 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
Autocad Autodesk 2020 (including) 2020.1.6 (excluding)
Autocad Autodesk 2021 (including) 2021.1.3 (excluding)
Autocad Autodesk 2022 (including) 2022.1.3 (excluding)
Autocad Autodesk 2023 (including) 2023.1.1 (excluding)
Autocad_advance_steel Autodesk 2020 (including) 2020.1.6 (excluding)
Autocad_advance_steel Autodesk 2021 (including) 2021.1.3 (excluding)
Autocad_advance_steel Autodesk 2022 (including) 2022.1.3 (excluding)
Autocad_advance_steel Autodesk 2023 (including) 2023.1.1 (excluding)
Autocad_architecture Autodesk 2020 (including) 2020.1.6 (excluding)
Autocad_architecture Autodesk 2021 (including) 2021.1.3 (excluding)
Autocad_architecture Autodesk 2022 (including) 2022.1.3 (excluding)
Autocad_architecture Autodesk 2023 (including) 2023.1.1 (excluding)
Autocad_civil_3d Autodesk 2020 (including) 2020.1.6 (excluding)
Autocad_civil_3d Autodesk 2021 (including) 2021.1.3 (excluding)
Autocad_civil_3d Autodesk 2022 (including) 2022.1.3 (excluding)
Autocad_civil_3d Autodesk 2023 (including) 2023.1.1 (excluding)
Autocad_electrical Autodesk 2020 (including) 2020.1.6 (excluding)
Autocad_electrical Autodesk 2021 (including) 2021.1.3 (excluding)
Autocad_electrical Autodesk 2022 (including) 2022.1.3 (excluding)
Autocad_electrical Autodesk 2023 (including) 2023.1.1 (excluding)
Autocad_lt Autodesk 2020 (including) 2020.1.6 (excluding)
Autocad_lt Autodesk 2021 (including) 2021.1.3 (excluding)
Autocad_lt Autodesk 2022 (including) 2022.1.3 (excluding)
Autocad_lt Autodesk 2023 (including) 2023.1.1 (excluding)
Autocad_map_3d Autodesk 2020 (including) 2020.1.6 (excluding)
Autocad_map_3d Autodesk 2021 (including) 2021.1.3 (excluding)
Autocad_map_3d Autodesk 2022 (including) 2022.1.3 (excluding)
Autocad_map_3d Autodesk 2023 (including) 2023.1.1 (excluding)
Autocad_mechanical Autodesk 2020 (including) 2020.1.6 (excluding)
Autocad_mechanical Autodesk 2021 (including) 2021.1.3 (excluding)
Autocad_mechanical Autodesk 2022 (including) 2022.1.3 (excluding)
Autocad_mechanical Autodesk 2023 (including) 2023.1.1 (excluding)
Autocad_mep Autodesk 2020 (including) 2020.1.6 (excluding)
Autocad_mep Autodesk 2021 (including) 2021.1.3 (excluding)
Autocad_mep Autodesk 2022 (including) 2022.1.3 (excluding)
Autocad_mep Autodesk 2023 (including) 2023.1.1 (excluding)
Autocad_plant_3d Autodesk 2020 (including) 2020.1.6 (excluding)
Autocad_plant_3d Autodesk 2021 (including) 2021.1.3 (excluding)
Autocad_plant_3d Autodesk 2022 (including) 2022.1.3 (excluding)
Autocad_plant_3d Autodesk 2023 (including) 2023.1.1 (excluding)

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