CVE-2024-45277 — @sap/hana-client
MEDIUMCVE-2024-45277 is a medium-severity (CVSS 4.3) CWE-1321 vulnerability in @sap/hana-client. A fix is available for @sap/hana-client — see the affected versions and patch details below.
SAP HANA Node.js client package vulnerable to Prototype Pollution
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-45277.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@sap/hana-clientnpmDescription
The SAP HANA Node.js client package versions from 2.0.0 before 2.21.31 is impacted by Prototype Pollution vulnerability allowing an attacker to add arbitrary properties to global object prototypes. This is due to improper user input sanitation when using the nestTables feature causing low impact on the availability of the application. This has no impact on Confidentiality and Integrity.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @sap/hana-client | ≥ 2.0.0&&< 2.21.31 | 2.21.31npm install @sap/hana-client@2.21.31 |
Affected Products
hana-clientsapDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sap/hana-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @sap/hana-client to 2.21.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45277 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.
Frequently Asked Questions
Is CVE-2024-45277 in your dependencies?
Find it across npm, including transitive dependencies.