Categories
CVE-2024-22051 critical CVSS 9.8

Vulnerability in commonmarker (CVE-2024-22051)

Summary

Vulnerability in commonmarker (CVE-2024-22051). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.23.4 or later.

Original description

The description as published by the source.

CommonMarker versions prior to 0.23.4 are at risk of an integer overflow vulnerability. This vulnerability can result in possibly unauthenticated remote attackers to cause heap memory corruption, potentially leading to an information leak or remote code execution, via parsing tables with marker rows that contain more than UINT16_MAX columns.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-22051 has been found in commonmarker.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade commonmarker to 0.23.4 or later.
If unsure, ask your IT team or search "commonmarker CVE-2024-22051" on the vendor's site.

CVE-2024-22051 (commonmarker) — CWE-190 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.23.4 — apply immediately
Workaround: The vulnerability exists in the table markdown extensions of cmark-gfm.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-190) exists in commonmarker.

📍 Affected scope

Check the vendor advisory for the affected versions of commonmarker.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 0.23.4.

🛡️ Workaround

Workaround: The vulnerability exists in the table markdown extensions of cmark-gfm.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'commonmarker' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'commonmarker' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で commonmarker を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    The vulnerability exists in the table markdown extensions of `cmark-gfm`.

    パッチが適用されるまでの応急処置として、The vulnerability exists in the table markdown extensions of cmark-gfm. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade commonmarker to 0.23.4

    ステージング環境で 0.23.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

RubyGems commonmarker
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.23.4"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details