Sandbox Bypass Leading to Arbitrary Code Execution in constantinople

published 2019-06-14 7y ago modified 2021-08-16 5y ago

cvss: 10.0; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

Versions of `constantinople` prior to 3.1.1 are vulnerable to a sandbox bypass which can lead to arbitrary code execution.

## Recommendation

Update to version 3.1.1 or later.

Patch / fix

fixed in 1 links 1

npm constantinople 3.1.1

github.com/pugjs/constantinople@01d409c commit

Is GHSA-4vmm-mhcq-4x9j in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	10.0	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	constantinople	<3.1.1	3.1.1

References

Sources

GitHub Advisory GHSA-4vmm-mhcq-4x9j

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.