LiveActive security incident?Get immediate response
CVE Record

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

A vulnerability has been identified in Solid Edge SE2022 (All versions < V222.0MP12), Solid Edge SE2023 (All versions < V223.0Update2). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted PAR files. This could allow an attacker to execute code in the context of the current process.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-24556 affects Siemens Solid Edge when it opens specially crafted PAR files. A malicious file could cause code to run inside the Solid Edge process. This is primarily a workstation and file-handling risk, not a remotely reachable server flaw, but it can still matter where engineering files come from customers, suppliers, or email.

Executive priority

Prioritize patching engineering workstations that handle external CAD files. The business risk is code execution through trusted design workflows, with potential data theft, workstation compromise, or disruption to engineering operations.

Technical view

Affected Solid Edge SE2022 versions before V222.0MP12 and SE2023 versions before V223.0Update2 contain a CWE-125 out-of-bounds read while parsing PAR files. The CVSS 3.1 score is 7.8, with local attack vector, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on engineering workstations running affected Solid Edge versions, especially where users open PAR files from external parties, shared repositories, email, or web downloads.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation. The CVSS vector includes proof-of-concept exploit maturity, but exploitation still requires a user to open a malicious PAR file locally.

Researcher notes

Key constraints are AV:L and UI:R: exploitation depends on local file parsing by the user. The source bundle identifies affected version ranges and fixed release thresholds, but does not provide deeper root-cause detail beyond the PAR parser out-of-bounds read.

Mitigation direction

  • Upgrade Solid Edge SE2022 to V222.0MP12 or later.
  • Upgrade Solid Edge SE2023 to V223.0Update2 or later.
  • Check Siemens SSA-491245 for the official update path and guidance.
  • Limit opening PAR files from untrusted external sources.
  • Apply attachment and file-transfer controls for unsolicited engineering files.

Validation and detection

  • Inventory Solid Edge installations and record exact SE2022 or SE2023 build versions.
  • Confirm no affected workstation remains below the fixed versions.
  • Review whether PAR files are accepted from external parties or email.
  • Check endpoint detections for suspicious Solid Edge process behavior.
  • Track remediation evidence against Siemens SSA-491245.
Prepared
Confidence
high
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-125: 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-24556 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-24556Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/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 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-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.