CVE-2023-50424 is a critical-severity (CVSS 9.1) vulnerability in com.sap.cloud.security:java-security. A fix is available for com.sap.cloud.security:java-security — see the affected versions and patch details below.
Escalation of Privileges in SAP BTP Security Services Integration Library ([Golang] github.com/sap/cloud-security-client-go)
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-50424 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
com.sap.cloud.security:java-security☕com.sap.cloud.security:java-security☕com.sap.cloud.security:spring-security☕com.sap.cloud.security:spring-security☕com.sap.cloud.security.xsuaa:spring-xsuaa☕com.sap.cloud.security.xsuaa:spring-xsuaaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
SAP BTP Security Services Integration Library ([Java] cloud-security-services-integration-library) allows under certain conditions an escalation of privileges. On successful exploitation, an unauthenticated attacker can obtain arbitrary permissions within the application.
Patches
Upgrade to patched version >= 2.17.0 or >= 3.3.0 We always recommend to upgrade to the latest released version.
Workarounds
No workarounds
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.sap.cloud.security:java-security | all versions | 2.17.0com.sap.cloud.security:java-security:2.17.0 |
| ☕Maven | com.sap.cloud.security:java-security | ≥ 3.0.0&&< 3.3.0 | 3.3.0com.sap.cloud.security:java-security:3.3.0 |
| ☕Maven | com.sap.cloud.security:spring-security | all versions | 2.17.0com.sap.cloud.security:spring-security:2.17.0 |
| ☕Maven | com.sap.cloud.security:spring-security | ≥ 3.0.0&&< 3.3.0 | 3.3.0com.sap.cloud.security:spring-security:3.3.0 |
| ☕Maven | com.sap.cloud.security.xsuaa:spring-xsuaa | all versions | 2.17.0com.sap.cloud.security.xsuaa:spring-xsuaa:2.17.0 |
| ☕Maven | com.sap.cloud.security.xsuaa:spring-xsuaa | ≥ 3.0.0&&< 3.3.0 | 3.3.0com.sap.cloud.security.xsuaa:spring-xsuaa:3.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.sap.cloud.security:java-security, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.sap.cloud.security:java-security to 2.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-50424 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-50424 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-50424. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2023-50424 in your dependencies?
O3 Security finds CVE-2023-50424 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.