Remote code execution via recursive prototype pollution
Published Apr 18, 2024 · Updated Aug 22, 2024
Prototype pollution in NORA Firebase Common 1.0.41 through 1.12.2 allows remote attackers to execute arbitrary code via crafted state data. updateStateInternal recursively copies enumerable updateState keys into the destination without rejecting proto, constructor, or prototype, allowing Object.prototype modification. The published proof of concept establishes process-wide prototype pollution, but it does not demonstrate the claimed arbitrary code execution consequence.
Summary
What happened
Prototype pollution in NORA Firebase Common 1.0.41 through 1.12.2 allows remote attackers to execute arbitrary code via crafted state data. updateStateInternal recursively copies enumerable updateState keys into the destination without rejecting proto, constructor, or prototype, allowing Object.prototype modification. The published proof of concept establishes process-wide prototype pollution, but it does not demonstrate the claimed arbitrary code execution consequence.
The record
- CVE
- CVE-2024-30564
- Published
- Apr 18, 2024
- Updated
- Aug 22, 2024
- Vendor
- Andrei Tatar
- Product
- NORA Firebase Common
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 18, 2024CVE publishedPublication date reported by the CVE source.
- Aug 22, 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=1.0.41 <=1.12.2
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
- CVE-2024-30564 updateState 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