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

Siemens

RUGGEDCOM RM1224 LTE(4G) EU

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-2025-23384 11 Mar 2025 < V8.2.1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-50572 12 Nov 2024 < V8.2 Update to V3.0.0 or later version Update reference ↗
CVE-2024-50561 12 Nov 2024 < V8.2 Update to V3.0.0 or later version Update reference ↗
CVE-2024-50560 12 Nov 2024 < V8.2 Update to V3.0.0 or later version Update reference ↗
CVE-2024-50559 12 Nov 2024 < V8.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-50558 12 Nov 2024 < V8.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-50557 12 Nov 2024 < V8.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-41978 13 Aug 2024 < V8.1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-41977 13 Aug 2024 < V8.1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-41976 13 Aug 2024 < V8.1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-49692 12 Dec 2023 < V7.2.2 Update to V7.2.2 or later version Update reference ↗
CVE-2023-49691 12 Dec 2023 < V8.0 Update to V3.0.2 or later version Update reference ↗
CVE-2023-44374 14 Nov 2023 < V8.0 Update to V3.0.0 or later version Update reference ↗
CVE-2023-44373 14 Nov 2023 < V8.0 Update to V6.6.0 or later version Update reference ↗
CVE-2023-44322 14 Nov 2023 < V8.0 Update to V3.0.0 or later version Update reference ↗
CVE-2023-44321 14 Nov 2023 < V8.1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-44320 14 Nov 2023 < V7.2.2 Update to V3.0.0 or later version Update reference ↗
CVE-2023-44319 14 Nov 2023 < V8.0 Update to V3.0.0 or later version Update reference ↗
CVE-2023-44318 14 Nov 2023 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-44317 14 Nov 2023 < V7.2.2 Update to V3.0.0 or later version Update reference ↗
CVE-2022-46143 13 Dec 2022 < V7.2; < V8.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-46142 13 Dec 2022 < V7.2 Update to V2.0.0 or later version Update reference ↗
CVE-2022-46140 13 Dec 2022 < V7.2 Update to V2.0.0 or later version Update reference ↗
CVE-2022-31766 11 Oct 2022 < V7.1.2 Update to V3.0.0 or later version Update reference ↗
CVE-2022-31765 11 Oct 2022 < V7.1.2 Update to V6.6.0 or later version Update reference ↗
CVE-2022-36325 10 Aug 2022 < V7.1.2 Update to V6.6.0 or later version Update reference ↗
CVE-2022-36324 10 Aug 2022 < V7.1.2 Update to V6.6.0 or later version Update reference ↗
CVE-2022-36323 10 Aug 2022 < V7.1.2 Update to V6.6.0 or later version Update reference ↗
CVE-2022-34821 12 Jul 2022 < V7.2 Update to V2.2.28 or later version 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.