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

Siemens

RUGGEDCOM CROSSBOW

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-2024-27947 14 May 2024 < V5.5 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-27946 14 May 2024 < V5.5 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-27945 14 May 2024 < V5.5 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-27944 14 May 2024 < V5.5 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-27943 14 May 2024 < V5.5 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-27942 14 May 2024 < V5.5 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-27941 14 May 2024 < V5.5 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-27940 14 May 2024 < V5.5 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-27939 14 May 2024 < V5.5 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-37373 8 Aug 2023 All versions < V5.4 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-37372 8 Aug 2023 All versions < V5.4 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-27411 8 Aug 2023 All versions < V5.4 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-27463 14 Mar 2023 All versions < V5.3 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-27462 14 Mar 2023 All versions < V5.3 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-27310 14 Mar 2023 All versions < V5.2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-27309 14 Mar 2023 All versions < V5.2 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.