Unauthorized access to data in @sap-cloud-sdk/coreGHSA-gp2f-254m-rh32
MEDIUMFix: SAP/cloud-sdk-js#1769GHSA-gp2f-254m-rh32 is a medium-severity (CVSS 5.9) Information Exposure vulnerability in @sap-cloud-sdk/core. 1 public exploit reference exists, so weaponization risk is real. A fix is available for @sap-cloud-sdk/core — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-gp2f-254m-rh32 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@sap-cloud-sdk/corenpmDescription
Impact
This affects applications on SAP Business Technology Platform that use the SAP Cloud SDK and enabled caching of destinations. In some cases, when user information was missing, destinations were cached without user information, allowing other users to retrieve the same destination with its permissions. By default, destination caching is disabled. If it is enabled the maximum lifetime is 5 minutes which limits the attack vector.
Patches
The problem was fixed by #1769 and #1770. The security for caching has been increased. The changes are released in version 1.52.0.
Workarounds
Disable destination caching (it is disabled by default).
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in https://github.com/SAP/cloud-sdk-js
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @sap-cloud-sdk/core | all versions | 1.52.0npm install @sap-cloud-sdk/core@1.52.0 |
Affected Products
cloud sdksapResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sap-cloud-sdk/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @sap-cloud-sdk/core to 1.52.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gp2f-254m-rh32 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-gp2f-254m-rh32 in your dependencies?
Find it across npm, including transitive dependencies.