pygmentize Remote Code Execution

published 2024-05-15 2y ago modified 2024-11-29 last yr.

cvss: 8.1; 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

pygmentize is prone to remote code execution due to an unsafe sanitazation of user input when passed to the `highlight` function.

Patch / fix

fixed in 1 links 1

packagist 3f/pygmentize 1.2

github.com/dedalozzo/pygmentize#3 pull request

Is GHSA-77mv-mp2j-gxxh 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	8.1	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
packagist	3f/pygmentize	<1.2	1.2

References

Sources

GitHub Advisory GHSA-77mv-mp2j-gxxh

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.