LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24566: A vulnerability has been identified in Solid Edge SE2022 (All versions < V222.0MP12), Solid Edge SE2022 (Al...

A vulnerability has been identified in Solid Edge SE2022 (All versions < V222.0MP12), Solid Edge SE2022 (All versions), Solid Edge SE2023 (All versions < V223.0Update2). The affected application is vulnerable to stack-based buffer while parsing specially crafted PAR files. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-19472)

LowCVSS 3.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2023-24566 affects Siemens Solid Edge when a user opens a specially crafted PAR file. The reported impact is code execution in the current Solid Edge process, but exploitation requires local user interaction and the CVSS score is low.

Executive priority

Treat this as a targeted workstation risk, not an emergency. Remediate during normal patch cycles unless CAD teams frequently process untrusted third-party PAR files, where priority should rise.

Technical view

The issue is a CWE-121 stack-based buffer overflow in Solid Edge PAR file parsing. Listed affected versions include Solid Edge SE2022 below V222.0MP12 and Solid Edge SE2023 below V223.0Update2, with one source entry ambiguously listing Solid Edge SE2022 all versions.

Likely exposure

Exposure is most likely on engineering workstations running affected Solid Edge SE2022 or SE2023 builds, especially where users open PAR files from customers, suppliers, or shared project repositories.

Exploitation context

The source bundle does not indicate known active exploitation, and KEV status is false. Abuse would require persuading a user to open a crafted PAR file locally; no network-reachable attack path is described.

Researcher notes

Evidence supports a local, user-assisted file parsing vulnerability. The affected-product text contains an ambiguous duplicate SE2022 entry, so validation should rely on Siemens SSA-491245 and exact installed build numbers.

Mitigation direction

  • Apply Siemens guidance from SSA-491245 and update affected Solid Edge installations.
  • Prioritize SE2022 below V222.0MP12 and SE2023 below V223.0Update2.
  • Restrict opening PAR files from untrusted external sources.
  • Quarantine suspicious CAD files until reviewed through normal security handling.
  • Confirm whether SE2022 remains affected where the advisory wording is ambiguous.

Validation and detection

  • Inventory Solid Edge installations and record exact SE2022 or SE2023 build versions.
  • Compare versions against V222.0MP12 and V223.0Update2 thresholds.
  • Review engineering workflows for externally supplied PAR files.
  • Check endpoint telemetry for Solid Edge crashes linked to PAR file handling.
  • Verify vendor advisory status before closing remediation tickets.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-24566 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C1.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.3Low
CVSS 3.1 vector shape for CVE-2023-24566Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SiemensSolid Edge SE2022All versions < V222.0MP12unknown
SiemensSolid Edge SE2022All versionsunknown
SiemensSolid Edge SE2023All versions < V223.0Update2unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.