Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY19 SECURITY RECORDS

Siemens

Solid Edge SE2022

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2023-24581 14 Feb 2023 All versions < V222.0MP12; All versions; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24566 14 Feb 2023 All versions < V222.0MP12; All versions; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24565 14 Feb 2023 All versions < V222.0MP12; All versions; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24564 14 Feb 2023 All versions < V222.0MP12; All versions; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24563 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24562 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24561 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24560 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24559 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24558 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24557 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24556 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24555 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24554 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24553 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24552 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24551 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24550 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24549 14 Feb 2023 All versions < V222.0MP12; All versions < V223.0Update2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.