CVE-2023-24845

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2023-08-08. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2023-28835 (ENISA EUVD) · GHSA-jmc7-cjhg-7q7v (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Siemens) lists Siemens RUGGEDCOM i800 versions before V4.3.8; Siemens RUGGEDCOM i800NC versions before V4.3.8; Siemens RUGGEDCOM i801 versions before V4.3.8 as affected, and 5 more products. No release containing a fix is confirmed on record.

A vulnerability has been identified in RUGGEDCOM i800, RUGGEDCOM i800NC, RUGGEDCOM i801, RUGGEDCOM i801NC, RUGGEDCOM i802, RUGGEDCOM i802NC, RUGGEDCOM i803, RUGGEDCOM i803NC, RUGGEDCOM M2100, RUGGEDCOM M2100F, RUGGEDCOM M2100NC, RUGGEDCOM M2200, RUGGEDCOM M2200F, RUGGEDCOM M2200NC, RUGGEDCOM M969, RUGGEDCOM M969F, RUGGEDCOM M969NC, RUGGEDCOM RMC30, RUGGEDCOM RMC30NC, RUGGEDCOM RMC8388 V4.X, RUGGEDCOM RMC8388 V5.X, RUGGEDCOM RMC8388NC V4.X, RUGGEDCOM RMC8388NC V5.X, RUGGEDCOM RP110, RUGGEDCOM RP110NC, RUGGEDCOM RS1600, RUGGEDCOM RS1600F, RUGGEDCOM RS1600FNC, RUGGEDCOM RS1600NC, RUGGEDCOM RS1600T, RUGGEDCOM RS1600TNC, RUGGEDCOM RS400, RUGGEDCOM RS400F, RUGGEDCOM RS400NC, RUGGEDCOM RS401, RUGGEDCOM RS401NC, RUGGEDCOM RS416, RUGGEDCOM RS416F, RUGGEDCOM RS416NC, RUGGEDCOM RS416NCv2 V4.X, RUGGEDCOM RS416NCv2 V5.X, RUGGEDCOM RS416P, RUGGEDCOM RS416PF, RUGGEDCOM RS416PNC, RUGGEDCOM RS416PNCv2 V4.X, RUGGEDCOM RS416PNCv2 V5.X, RUGGEDCOM RS416Pv2 V4.X, RUGGEDCOM RS416Pv2 V5.X, RUGGEDCOM RS416v2 V4.X, RUGGEDCOM RS416v2 V5.X, RUGGEDCOM RS8000, RUGGEDCOM RS8000A, RUGGEDCOM RS8000ANC, RUGGEDCOM RS8000H, RUGGEDCOM RS8000HNC, RUGGEDCOM RS8000NC, RUGGEDCOM RS8000T, RUGGEDCOM RS8000TNC, RUGGEDCOM RS900, RUGGEDCOM RS900, RUGGEDCOM RS900 (32M) V4.X, RUGGEDCOM RS900 (32M) V5.X, RUGGEDCOM RS900F, RUGGEDCOM RS900G, RUGGEDCOM RS900G (32M) V4.X, RUGGEDCOM RS900G (32M) V5.X, RUGGEDCOM RS900GF, RUGGEDCOM RS900GNC, RUGGEDCOM RS900GNC(32M) V4.X, RUGGEDCOM RS900GNC(32M) V5.X, RUGGEDCOM RS900GP, RUGGEDCOM RS900GPF, RUGGEDCOM RS900GPNC, RUGGEDCOM RS900L, RUGGEDCOM RS900L, RUGGEDCOM RS900LNC, RUGGEDCOM RS900LNC, RUGGEDCOM RS900M-GETS-C01, RUGGEDCOM RS900M-GETS-XX, RUGGEDCOM RS900M-STND-C01, RUGGEDCOM RS900M-STND-XX, RUGGEDCOM RS900MNC-GETS-C01, RUGGEDCOM RS900MNC-GETS-XX, RUGGEDCOM RS900MNC-STND-XX, RUGGEDCOM RS900MNC-STND-XX-C01, RUGGEDCOM RS900NC, RUGGEDCOM RS900NC, RUGGEDCOM RS900NC(32M) V4.X, RUGGEDCOM RS900NC(32M) V5.X, RUGGEDCOM RS900W, RUGGEDCOM RS910, RUGGEDCOM RS910L, RUGGEDCOM RS910LNC, RUGGEDCOM RS910NC, RUGGEDCOM RS910W, RUGGEDCOM RS920L, RUGGEDCOM RS920LNC, RUGGEDCOM RS920W, RUGGEDCOM RS930L, RUGGEDCOM RS930LNC, RUGGEDCOM RS930W, RUGGEDCOM RS940G, RUGGEDCOM RS940GF, RUGGEDCOM RS940GNC, RUGGEDCOM RS969, RUGGEDCOM RS969NC, RUGGEDCOM RSG2100, RUGGEDCOM RSG2100 (32M) V4.X, RUGGEDCOM RSG2100 (32M) V5.X, RUGGEDCOM RSG2100F, RUGGEDCOM RSG2100NC, RUGGEDCOM RSG2100NC(32M) V4.X, RUGGEDCOM RSG2100NC(32M) V5.X, RUGGEDCOM RSG2100P, RUGGEDCOM RSG2100P (32M) V4.X, RUGGEDCOM RSG2100P (32M) V5.X, RUGGEDCOM RSG2100PF, RUGGEDCOM RSG2100PNC, RUGGEDCOM RSG2100PNC (32M) V4.X, RUGGEDCOM RSG2100PNC (32M) V5.X, RUGGEDCOM RSG2200, RUGGEDCOM RSG2200F, RUGGEDCOM RSG2200NC, RUGGEDCOM RSG2288 V4.X, RUGGEDCOM RSG2288 V5.X, RUGGEDCOM RSG2288NC V4.X, RUGGEDCOM RSG2288NC V5.X, RUGGEDCOM RSG2300 V4.X, RUGGEDCOM RSG2300 V5.X, RUGGEDCOM RSG2300F, RUGGEDCOM RSG2300NC V4.X, RUGGEDCOM RSG2300NC V5.X, RUGGEDCOM RSG2300P V4.X, RUGGEDCOM RSG2300P V5.X, RUGGEDCOM RSG2300PF, RUGGEDCOM RSG2300PNC V4.X, RUGGEDCOM RSG2300PNC V5.X, RUGGEDCOM RSG2488 V4.X, RUGGEDCOM RSG2488 V5.X, RUGGEDCOM RSG2488F, RUGGEDCOM RSG2488NC V4.X, RUGGEDCOM RSG2488NC V5.X, RUGGEDCOM RSG907R, RUGGEDCOM RSG908C, RUGGEDCOM RSG909R, RUGGEDCOM RSG910C, RUGGEDCOM RSG920P V4.X, RUGGEDCOM RSG920P V5.X, RUGGEDCOM RSG920PNC V4.X, RUGGEDCOM RSG920PNC V5.X, RUGGEDCOM RSL910, RUGGEDCOM RSL910NC, RUGGEDCOM RST2228, RUGGEDCOM RST2228P, RUGGEDCOM RST916C, RUGGEDCOM RST916P. The affected products insufficiently block data from being forwarded over the mirror port into the mirrored network. An attacker could use this behavior to transmit malicious packets to systems in the mirrored network, possibly influencing their configuration and runtime behavior.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 8, 2023

Last Modified

August 12, 2025

Advisory Details (2)

Auto-updated Aug 1, 2026
No fix on record yet.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 74× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 249 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 09:08 UTCEG score recompute
  2. 2026-11-02 09:08 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-11-01 10:19 UTCEG score recompute
  5. 2026-11-01 10:19 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-10-31 11:29 UTCEG score recompute
  8. 2026-10-31 11:29 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-30 12:39 UTCEG score recompute
  11. 2026-10-30 12:39 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-29 13:49 UTCEG score recompute
  14. 2026-10-29 13:48 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-28 14:57 UTCEG score recompute
  17. 2026-10-28 14:57 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-27 15:47 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-10-26 16:56 UTCEG score recompute
  21. 2026-10-26 16:55 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-25 17:51 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-25 17:47 UTCEG score recompute
  25. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 74 more
  1. 2026-10-24 18:30 UTCEG score recompute
  2. 2026-10-24 18:30 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-10-23 19:38 UTCEG score recompute
  5. 2026-10-23 19:38 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-10-22 20:49 UTCEG score recompute
  8. 2026-10-22 20:49 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-21 21:56 UTCEG score recompute
  11. 2026-10-21 21:56 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-20 22:49 UTCEG score recompute
  14. 2026-10-20 22:49 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-19 23:30 UTCEG score recompute
  17. 2026-10-19 23:30 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-18 22:54 UTCEG score recompute
  20. 2026-10-18 22:54 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-18 08:10 UTCEG score recompute
  22. 2026-10-18 00:04 UTCEG score recompute
  23. 2026-10-18 00:03 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-17 01:11 UTCEG score recompute
  26. 2026-10-17 01:10 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  27. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  28. 2026-10-16 01:17 UTCEG score recompute
  29. 2026-10-16 01:16 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  30. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-10-14 20:25 UTCEG score recompute
  32. 2026-10-14 20:25 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  33. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  34. 2026-10-13 16:39 UTCEG score recompute
  35. 2026-10-13 16:38 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  36. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-10-12 17:31 UTCEG score recompute
  38. 2026-10-12 17:31 UTCGHSA enrichmentGHSA-jmc7-cjhg-7q7v · GitHub severity CRITICAL · GitHub CVSS 9.1
  39. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  40. 2026-10-11 21:58 UTCEG score recompute
  41. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  42. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  43. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  44. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  45. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  46. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  47. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  48. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  49. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  50. 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  51. 2026-10-01 19:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  52. 2026-09-30 16:18 UTCEG score recompute
  53. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  54. 2026-09-29 15:16 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  56. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  57. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  58. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  59. 2026-09-22 14:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  60. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  61. 2026-09-19 15:38 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  62. 2026-09-18 19:25 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  63. 2026-09-17 19:24 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  64. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  65. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  70. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  72. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  73. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  74. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile

Frequently asked(5)

What is CVE-2023-24845?
CVE-2023-24845 is a critical-severity vulnerability; its CVE record was published on August 8, 2023. A vulnerability has been identified in RUGGEDCOM i800, RUGGEDCOM i800NC, RUGGEDCOM i801, RUGGEDCOM i801NC, RUGGEDCOM i802, RUGGEDCOM i802NC, RUGGEDCOM i803, RUGGEDCOM i803NC, RUGGEDCOM M2100, RUGGEDCOM M2100F, RUGGEDCOM M2100NC, RUGGEDCOM M2200, RUGGEDCOM M2200F, RUGGEDCOM M2200NC, RUGGEDCOM M969,…
When was the CVE record for CVE-2023-24845 published?
The CVE record for CVE-2023-24845 was published on August 8, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 12, 2025; the record at its source may have been updated since.
Is CVE-2023-24845 actively exploited?
CVE-2023-24845 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-24845?
CVE-2023-24845 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2023-24845?
No fix for CVE-2023-24845 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Siemens) lists Siemens RUGGEDCOM i800 versions before V4.3.8; Siemens RUGGEDCOM i800NC versions before V4.3.8; Siemens RUGGEDCOM i801 versions before V4.3.8 as affected, and 5 more products. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-24845

Explore →

Is Your Infrastructure Affected by CVE-2023-24845?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.