Comrak vulnerable to production of excessive output when parsing Markdown (GHSL-2023-048)

published 2023-03-28 3y ago modified 2023-03-28 3y ago

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

### Impact

comrak is vulnerable to the upstream cmark issue, ["Issue revealed by fuzzer"](https://github.com/commonmark/cmark/issues/354). A large number of references in a markdown document can trigger an overly large response.

### Patches

0.17.0 contains https://github.com/kivikakk/comrak/commit/70f97f3ea4eae30ffbd1b94c764a3de2f1c41d2a, which limits reference output to a 100Kb maximum.

### Workarounds

n/a

### References

* https://github.com/commonmark/cmark/issues/354

Patch / fix

fixed in 1 links 2

crates.io comrak 0.17.0

github.com/kivikakk/comrak@70f97f3 commit
github.com/kivikakk/comrak/releases/tag/0.17.0 release

Is GHSA-xxmq-4vph-956w 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	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem	package	affected	fixed in
crates.io	comrak	<0.17.0	0.17.0

References

Sources

GitHub Advisory GHSA-xxmq-4vph-956w

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.