Code execution via request prototype pollution
Published Jul 1, 2024 · Updated Aug 2, 2024
Prototype pollution in CafeBazaar Hod 0.4.14 allows remote attackers to execute code or crash the service through request(). The request() function processes an object containing proto without blocking that special property, allowing attacker-supplied values to alter Object.prototype and affect inherited properties application-wide. No authentication or user interaction is required, but code execution or a crash depends on a reachable request() call and a usable application gadget.
Summary
What happened
Prototype pollution in CafeBazaar Hod 0.4.14 allows remote attackers to execute code or crash the service through request(). The request() function processes an object containing proto without blocking that special property, allowing attacker-supplied values to alter Object.prototype and affect inherited properties application-wide. No authentication or user interaction is required, but code execution or a crash depends on a reachable request() call and a usable application gadget.
The record
- CVE
- CVE-2024-39015
- Published
- Jul 1, 2024
- Updated
- Aug 2, 2024
- Vendor
- CafeBazaar
- Product
- Hod
- Classifications
- CWE-94, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.414
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- request() __proto__ prototype-pollution proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo