GHSA-48wp-p9qv-4j64 json
Commonmarker vulnerable to to several quadratic complexity bugs that may lead to denial of service
published 3y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
## Impact
Several quadratic complexity bugs in commonmarker's underlying [`cmark-gfm`](https://github.com/github/cmark-gfm) library may lead to unbounded resource exhaustion and subsequent denial of service.
The following vulnerabilities were addressed:
* [CVE-2023-24824](https://github.com/github/cmark-gfm/security/advisories/GHSA-66g8-4hjf-77xh) * [CVE-2023-26485](https://github.com/github/cmark-gfm/security/advisories/GHSA-r8vr-c48j-fcc5)
For more information, consult the release notes for version [`0.23.0.gfm.10`](https://github.com/github/cmark-gfm/releases/tag/0.29.0.gfm.10) and [`0.23.0.gfm.11`](https://github.com/github/cmark-gfm/releases/tag/0.29.0.gfm.11).
## Mitigation
Users are advised to upgrade to commonmarker version [`0.23.9`](https://rubygems.org/gems/commonmarker/versions/0.23.9).
Patch / fix
- rubygems commonmarker 0.23.9
Is GHSA-48wp-p9qv-4j64 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | commonmarker | <0.23.9 |
0.23.9 |
References
-
github.com
/gjtorikian/commonmarker/pull/236
web
-
github.com
/github/cmark-gfm/security/advisories/GHSA-66g8-4hjf-77xh
web
-
github.com
/github/cmark-gfm/security/advisories/GHSA-r8vr-c48j-fcc5
web
-
github.com
/gjtorikian/commonmarker/security/advisories/GHSA-48wp-p9qv-4j64
web
-
github.com
/github/cmark-gfm/releases/tag/0.29.0.gfm.10
web
-
github.com
/github/cmark-gfm/releases/tag/0.29.0.gfm.11
web
-
github.com
/gjtorikian/commonmarker
package
-
github.com
/gjtorikian/commonmarker/releases/tag/v0.23.9
web
Sources
- GitHub Advisory GHSA-48wp-p9qv-4j64
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.