CVE-2023-50422

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.4% (72nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 9.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2023-12-13) is not newer than that change (2026-06-17), so it does not.

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

Also known asEUVD-2023-3112 (ENISA EUVD) · GHSA-59c9-pxq8-9c73 (GitHub Security Advisories) · GO-2023-2400 (OSV.dev)Source: ENISA EUVD

9.8EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

SAP BTP Security Services Integration Library ([Java] cloud-security-services-integration-library) - versions below 2.17.0 and versions from 3.0.0 to before 3.3.0, allow under certain conditions an escalation of privileges. On successful exploitation, an unauthenticated attacker can obtain arbitrary permissions within the application.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.4% × 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 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
1.4%
EPSS %ILE
72nd
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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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: 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 or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (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

December 12, 2023

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Nov 1, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

CVE-2023-50422 · Advisory · SAP/cloud-security-services-integration-library · GitHub

https://github.com/SAP/cloud-security-services-integration-library/security/advisories/GHSA-59c9-pxq8-9c73
Web page

GitHub - SAP/cloud-security-services-integration-library: Integration libraries and samples for authenticating users and clients bound to XSUAA authentication and authorization service or Identity authentication service. · GitHub

https://github.com/SAP/cloud-security-services-integration-library/
Web page

Maven Repository: com.sap.cloud.security » spring-security

https://mvnrepository.com/artifact/com.sap.cloud.security/spring-security
Web page

Maven Repository: com.sap.cloud.security » java-security

https://mvnrepository.com/artifact/com.sap.cloud.security/java-security
Web page

Maven Repository: com.sap.cloud.security.xsuaa » spring-xsuaa

https://mvnrepository.com/artifact/com.sap.cloud.security.xsuaa/spring-xsuaa

Vendor Advisories for CVE-2023-50422(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavencom.sap.cloud.security:java-security @ 2.17.0 (fixes < 2.17.0)—ghsa
mavencom.sap.cloud.security:java-security @ 3.3.0 (fixes >= 3.0.0, < 3.3.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 2 ecosystems)
Maven(3)
PackageVulnerable rangeFix by version rangeDependents
com.sap.cloud.security:java-security3.0.0 ... 3.2.1 (8 versions)
  • every version up to 2.17.0: fixed in 2.17.0
  • 3.0.0 up to 3.3.0: fixed in 3.3.0
—
com.sap.cloud.security:spring-security3.0.0 ... 3.2.1 (8 versions)
  • every version up to 2.17.0: fixed in 2.17.0
  • 3.0.0 up to 3.3.0: fixed in 3.3.0
—
com.sap.cloud.security.xsuaa:spring-xsuaa3.0.0 ... 3.2.1 (8 versions)
  • every version up to 2.17.0: fixed in 2.17.0
  • 3.0.0 up to 3.3.0: fixed in 3.3.0
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/sap/cloud-security-client-go—
  • every version up to 0.17.0: fixed in 0.17.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 45× 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 277 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 177 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-50422?
CVE-2023-50422 is a critical-severity vulnerability; its CVE record was published on December 12, 2023. SAP BTP Security Services Integration Library ([Java] cloud-security-services-integration-library) - versions below 2.17.0 and versions from 3.0.0 to before 3.3.0, allow under certain conditions an escalation of privileges. On successful exploitation, an unauthenticated attacker can obtain…
When was the CVE record for CVE-2023-50422 published?
The CVE record for CVE-2023-50422 was published on December 12, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2023-50422 actively exploited?
CVE-2023-50422 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-50422?
CVE-2023-50422 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-50422?
A fix for CVE-2023-50422 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-50422 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-50422

Explore →

Is Your Infrastructure Affected by CVE-2023-50422?

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