Information Disclosure in @sap-cloud-sdk/core (CVE-2021-41251)
Summary
Vulnerability in @sap-cloud-sdk/core (CVE-2021-41251). Confidential information can be exposed externally. Mitigation: upgrade to 1.52.0 or later.
Original description
The description as published by the source.
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
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-41251 has been found in @sap-cloud-sdk/core.
Confidential information can be exposed externally.
What to do: upgrade @sap-cloud-sdk/core to 1.52.0 or later.
If unsure, ask your IT team or search "@sap-cloud-sdk/core CVE-2021-41251" on the vendor's site.
CVE-2021-41251 (@sap-cloud-sdk/core) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.52.0 — apply immediately
Workaround: Disable destination caching (it is disabled by default).
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in @sap-cloud-sdk/core.
Check the vendor advisory for the affected versions of @sap-cloud-sdk/core.
Severity: ?. Confidential information can be exposed externally.
Update to 1.52.0.
Workaround: Disable destination caching (it is disabled by default).
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@sap-cloud-sdk/core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@sap-cloud-sdk/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@sap-cloud-sdk/coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Disable destination caching (it is disabled by default).パッチが適用されるまでの応急処置として、Disable destination caching (it is disabled by default). を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @sap-cloud-sdk/core to 1.52.0ステージング環境で 1.52.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com