CVE-2023-2564

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2023-34042 (ENISA EUVD) · GHSA-h5q9-8q57-gqh2 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 41%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

OS Command Injection in GitHub repository sbs20/scanservjs prior to v2.27.0.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation41% × 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
41%
EPSS %ILE
98th
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
41% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

May 7, 2023

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Nov 8, 2026
Patch available. Sources: github_pr.
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.dev/bounties/d13113ad-a107-416b-acc1-01e4c16ec461
GitHub pull request Patch Available

SECURITY: CommandBuilder fixes

Patch available: sbs20/scanservjs v2.27.0 (PR #606 merged 2023-05-07)

https://github.com/sbs20/scanservjs/pull/606/commits/d51fd52c1569813990b8f74e64ae6979c665dca1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 58× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 253 rows 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. None are among the latest 100 rows. The 153 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-2564?
CVE-2023-2564 is a critical-severity vulnerability; its CVE record was published on May 7, 2023. OS Command Injection in GitHub repository sbs20/scanservjs prior to v2.27.0.
When was the CVE record for CVE-2023-2564 published?
The CVE record for CVE-2023-2564 was published on May 7, 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-2564 actively exploited?
CVE-2023-2564 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 41% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-2564?
CVE-2023-2564 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2023-2564?
A fix for CVE-2023-2564 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2023-2564?

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

Book a Demo →Browse All CVEs