CVE-2023-52236

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

A vulnerability has been identified in RUGGEDCOM i800 (All versions), RUGGEDCOM i801 (All versions), RUGGEDCOM i802 (All versions), RUGGEDCOM i803…

CVE-2023-522363 of 4 sources documented this

rank 18 = 0 + 18 + 0 + 0 + 0

rank@v1 · backlog

Exploitation evidence0/40EPSS 0.00204

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00204 · without this subject the record ranks 18

Impact18/25CVSS 7.0, from the CNA

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.0, from the CNA · without this subject the record ranks 0

Movement0/15no persisting rise in 365 days

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days · without this subject the record ranks 18

Blast radius0/100 products in the CPE ranges

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges · without this subject the record ranks 18

Obligation0/10no CISA due date

Someone else already set the date

CISA KEV remediation due date

no CISA due date · without this subject the record ranks 18

Hindsight · the state

Severity7 HIGHreceipt

Harmunauthenticated · networkreceipt

Exploitationnone in held sources

Defenseno fix version held

Movementrisenreceipt

PLATEAUMinimal movement since 2025-07-08, 458 days at 0.00, as of 2026-10-09. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Which product do you run? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Choose your product above to watch it.

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · high attack complexityreceipt

ImpactComplete confidentiality loss; partial integrity and availability lossreceipt

Scored fromCVSS v3.1 · the CNA's vectorreceipt

Weakness classCWE-327 Use of a Broken or Risky Cryptographic Algorithmreceipt

Published consequencesCWE-327: Confidentiality: Read Application Data; Integrity: Modify Application Data; Accountability, Non-Repudiation: Hide Activitiescwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 9 Oct 2026.

Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived

Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

RUNG 1Nothing observed in held sources
RUNG 2Proof-of-concept published
RUNG 3Exploited in the wild · CISA KEV listed
RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7 HIGHreceipt

Exploit probability0.00204 · top 90% of all CVEsreceipt

Assigned bysiemensreceipt

Recorded changes18 · last 17 Oct 2026derived

Affected & Fixed Versions as published

Affected productSiemens RUGGEDCOM i800; Siemens RUGGEDCOM i801; Siemens RUGGEDCOM i802; Siemens RUGGEDCOM i803; Siemens RUGGEDCOM M2100; Siemens RUGGEDCOM M2200; Siemens RUGGEDCOM M969; Siemens RUGGEDCOM RMC30…receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Unaudited dollar value2 of 3 inputs carry a receipt

Exposure$8,150over the next 30 days, if this record is yours

Movementno material movementthe record holds only daily drift and scoring model releases

Basisassumeda published average, not your estate

$8,150 = $4.99M incident cost x 0.8004932139359172 exposure x 0.00204 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Attack path

What it is stated by the CNA

A vulnerability has been identified in RUGGEDCOM i800 (All versions), RUGGEDCOM i801 (All versions), RUGGEDCOM i802 (All versions), RUGGEDCOM i803 (All versions), RUGGEDCOM M2100 (All versions), RUGGEDCOM M2200 (All versions), RUGGEDCOM M969 (All versions), RUGGEDCOM RMC30 (All versions), RUGGEDCOM RMC8388 V4.X (All versions), RUGGEDCOM RMC8388 V5.X (All versions < V5.10.0), RUGGEDCOM RP110 (All versions), RUGGEDCOM RS1600 (All versions), RUGGEDCOM RS1600F (All versions), RUGGEDCOM RS1600T (All versions), RUGGEDCOM RS400 (All versions), RUGGEDCOM RS401 (All versions), RUGGEDCOM RS416 (All versions), RUGGEDCOM RS416P (All versions), RUGGEDCOM RS416Pv2 V4.X (All versions), RUGGEDCOM RS416Pv2 V receipt

Read the rest of the CNA's description

5.X (All versions < V5.10.0), RUGGEDCOM RS416v2 V4.X (All versions), RUGGEDCOM RS416v2 V5.X (All versions < V5.10.0), RUGGEDCOM RS8000 (All versions), RUGGEDCOM RS8000A (All versions), RUGGEDCOM RS8000H (All versions), RUGGEDCOM RS8000T (All versions), RUGGEDCOM RS900 (All versions), RUGGEDCOM RS900 (32M) V4.X (All versions), RUGGEDCOM RS900 (32M) V5.X (All versions < V5.10.0), RUGGEDCOM RS900G (All versions), RUGGEDCOM RS900G (32M) V4.X (All versions), RUGGEDCOM RS900G (32M) V5.X (All versions < V5.10.0), RUGGEDCOM RS900GP (All versions), RUGGEDCOM RS900L (All versions), RUGGEDCOM RS900M-GETS-C01 (All versions), RUGGEDCOM RS900M-GETS-XX (All versions), RUGGEDCOM RS900M-STND-C01 (All versions), RUGGEDCOM RS900M-STND-XX (All versions), RUGGEDCOM RS900W (All versions), RUGGEDCOM RS910 (All versions), RUGGEDCOM RS910L (All versions), RUGGEDCOM RS910W (All versions), RUGGEDCOM RS920L (All versions), RUGGEDCOM RS920W (All versions), RUGGEDCOM RS930L (All versions), RUGGEDCOM RS930W (All versions), RUGGEDCOM RS940G (All versions), RUGGEDCOM RS969 (All versions), RUGGEDCOM RSG2100 (All versions), RUGGEDCOM RSG2100 (32M) V4.X (All versions), RUGGEDCOM RSG2100 (32M) V5.X (All versions < V5.10.0), RUGGEDCOM RSG2100P (All versions), RUGGEDCOM RSG2100P (32M) V4.X (All versions), RUGGEDCOM RSG2100P (32M) V5.X (All versions < V5.10.0), RUGGEDCOM RSG2200 (All versions), RUGGEDCOM RSG2288 V4.X (All versions), RUGGEDCOM RSG2288 V5.X (All versions < V5.10.0), RUGGEDCOM RSG2300 V4.X (All versions), RUGGEDCOM RSG2300 V5.X (All versions < V5.10.0), RUGGEDCOM RSG2300P V4.X (All versions), RUGGEDCOM RSG2300P V5.X (All versions < V5.10.0), RUGGEDCOM RSG2488 V4.X (All versions), RUGGEDCOM RSG2488 V5.X (All versions < V5.10.0), RUGGEDCOM RSG907R (All versions < V5.10.0), RUGGEDCOM RSG908C (All versions < V5.10.0), RUGGEDCOM RSG909R (All versions < V5.10.0), RUGGEDCOM RSG910C (All versions < V5.10.0), RUGGEDCOM RSG920P V4.X (All versions), RUGGEDCOM RSG920P V5.X (All versions < V5.10.0), RUGGEDCOM RSL910 (All versions < V5.10.0), RUGGEDCOM RST2228 (All versions < V5.10.0), RUGGEDCOM RST2228P (All versions < V5.10.0), RUGGEDCOM RST916C (All versions < V5.10.0), RUGGEDCOM RST916P (All versions < V5.10.0). The affected products support insecure cryptographic algorithms. An attacker could leverage these legacy algorithms to achieve a man-in-the-middle attack or impersonate communicating parties.

NVD's analysis a second authority

weakness: CWE-327
also scored by: productcert@siemens.com 6.1 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X ·…

check it yourself cert-portal.siemens.com receipt

Movement the material steps

8 Jul 20250.00035

15 Jun 20260.00174 · scoring model v2026.06.15

9 Oct 20260.00204

Show all 18 observations

8 Jul 20250.00035

9 Jul 20250.00025

14 Jul 20250.0002

9 Aug 20250.00021

14 Sep 20250.00022

7 Nov 20250.00029

4 Dec 20250.00018

16 Dec 20250.00021

1 Feb 20260.00024

11 Feb 20260.00022

13 Mar 20260.00024

24 Mar 20260.00032

3 Apr 20260.00035

24 Apr 20260.00038

4 May 20260.00139

15 Jun 20260.00174

28 Sep 20260.0019

9 Oct 20260.00204

18 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

The record had been public for 1 year, 3 months when this index was last written.

Published 2025-07-08 receipt · Index as of 2026-10-09 derived

Siblings and hubs

Records related to this one

No record cites this identifier and it carries no alias. Its defect family is below.

Its defect family

siemens ruggedcom i800

CVE-2025-41223

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

The whole family, and what merged it

Nothing we hold separates this record from the others in its defect family. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

Every CVE we hold for Siemens Added to CISA KEV this week The whole index

These are index-wide views, not findings about CVE-2023-52236.

What usually comes next

Brief on CVE-2023-52236Held facts, dated and print-ready. Sign in to add the researched section.What moved across the whole index this week?The material set, not the catalogue.Do we run Siemens RUGGEDCOM i800?Match a product list against what we hold. Product names, not versions.

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.