Prototype pollution via unsafe result-object creation
Published Apr 10, 2024 · Updated Aug 22, 2024
Prototype pollution in Sidorares MySQL2 before 3.9.4 allows remote attackers to alter result-object prototypes via crafted field names. The generated text and binary parsers placed database-derived field names onto ordinary JavaScript objects, allowing constructor or prototype keys to affect inherited state. Exploitation requires application-controlled queries or a malicious MySQL server to supply crafted result metadata; successful attacks alter application object state, with no reported confidentiality impact.
Summary
What happened
Prototype pollution in Sidorares MySQL2 before 3.9.4 allows remote attackers to alter result-object prototypes via crafted field names. The generated text and binary parsers placed database-derived field names onto ordinary JavaScript objects, allowing constructor or prototype keys to affect inherited state. Exploitation requires application-controlled queries or a malicious MySQL server to supply crafted result metadata; successful attacks alter application object state, with no reported confidentiality impact.
The record
- CVE
- CVE-2024-21509
- Published
- Apr 10, 2024
- Updated
- Aug 22, 2024
- Vendor
- Sidorares
- Product
- MySQL2
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 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=0 <3.9.4
What conditions does exploitation require?
What is affected?
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
- User-defined database connection demonstrationproof 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