cmark-gfm

Every one of the 10 is a mark on the map. Named now: 1 to 10, most at risk first.

1. Integer overflow in table parsing extension leads to heap memory corruptionCVE-2022-24724github · CVSS 8.8 · 4.5% likely

   CWE-190

2. Uncontrolled Resource Consumption in cmark-gfmCVE-2022-39209github · CVSS 7.5 · 2.3% likely

   CWE-4001 bounty report

3. Denial of service in table parsing in cmark-gfmCVE-2020-5238github · CVSS 6.5 · 1.6% likely

   CWE-20

4. cmark-gfm Quadratic complexity bug in handle_close_bracket may lead to a denial of serviceCVE-2023-22486github · CVSS 3.5 · 1.1% likely

   CWE-407

5. cmark-gfm Quadratic complexity bugs may lead to a denial of serviceCVE-2023-22483github · CVSS 3.5 · 1.1% likely

   CWE-400

6. Quadratic complexity may lead to a denial of service in cmark-gfmCVE-2023-24824github · CVSS 5.3 · 1.0% likely

   CWE-407

7. Quadratic complexity may lead to a denial of service in cmark-gfmCVE-2023-26485github · CVSS 5.3 · 1.0% likely

   CWE-407

8. Inefficient Quadratic complexity bug in handle_pointy_brace may lead to a denial of serviceCVE-2023-22484github · CVSS 3.5 · 1.0% likely

   CWE-407

9. cmark-gfm out-of-bounds read in validate_protocolCVE-2023-22485github · CVSS 5.3 · 0.7% likely

   CWE-125

10. Quadratic complexity bugs may lead to a denial of serviceCVE-2023-37463github · CVSS 6.4 · 0.7% likely

    CWE-400

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.