Arbitrary code execution via LiteralMap prototype pollution
Published Oct 17, 2023 · Updated Sep 13, 2024
Prototype pollution in Relative Synchrony 2.0.1 through 2.4.3 allows local users to execute arbitrary code through crafted JavaScript. The LiteralMap transformer accepts a proto property and places an attacker-controlled parser path on Object.prototype, which Prettier later resolves with require(). Exploitation requires processing the crafted file under Node.js with the legacy proto accessor enabled, and code runs with the Synchrony process's privileges.
Summary
What happened
Prototype pollution in Relative Synchrony 2.0.1 through 2.4.3 allows local users to execute arbitrary code through crafted JavaScript. The LiteralMap transformer accepts a proto property and places an attacker-controlled parser path on Object.prototype, which Prettier later resolves with require(). Exploitation requires processing the crafted file under Node.js with the legacy proto accessor enabled, and code runs with the Synchrony process's privileges.
The record
- CVE
- CVE-2023-45811
- Published
- Oct 17, 2023
- Updated
- Sep 13, 2024
- Vendor
- Relative
- Product
- Synchrony
- Classifications
- CWE-1321, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 17, 2023CVE publishedPublication date reported by the CVE source.
- Sep 13, 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=>= 2.0.1, < 2.4.4
- Affected versionversion=2.0.1 <2.4.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
- Synchrony LiteralMap proof of conceptfunctional · 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