← Back
CVE-2024-27281
Unsafe Deserialization in rdoc (CVE-2024-27281)
Summary
vulnerability in rdoc (CVE-2024-27281). Risk of unauthorized operations or information disclosure. Exploitable via ``rdoc``. Mitigation: upgrade to `6.6.3.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-27281** has been found in rdoc.
Attackers can target a specific entry point like ``rdoc`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade rdoc to **6.6.3.1** or later.
If unsure, ask your IT team or search "rdoc CVE-2024-27281" on the vendor's site.
CVE-2024-27281 (rdoc) — CWE-502 /
Attack vector: local / unauthenticated
Attack surface: `rdoc` / `Gemfile`
Patched: `6.6.3.1` — apply immediately
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
**unsafe deserialization** (CWE-502) exists in rdoc. Attackers reach the vulnerable code path via ``rdoc`` without authentication.
📍 Affected scope
rdoc — . Attack surface: `rdoc` / `Gemfile`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.6.3.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'rdoc' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'rdoc' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `rdoc` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade rdoc to 6.6.3.1ステージング環境で 6.6.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
RubyGems
rdoc
[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.0"},{"fixed":"6.6.3.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-27281
- package https://github.com/ruby/rdoc
- web https://github.com/ruby/rdoc/commit/1254b0066f312ddbf7fae7a195e66ce5b3bc6656
- web https://github.com/ruby/rdoc/commit/32ff6ba0bebd8ea26f569da5fd23be2937f6a644
- web https://github.com/ruby/rdoc/commit/48617985e9fbc2825219d55f04e3e0e98d2923be
- web https://github.com/ruby/rdoc/commit/811f125a4a0cc968e3eb18e16ea6c1a3b49a11bf
- web https://github.com/ruby/rdoc/commit/a5de13bf0f0c26f8e764e82b5bf4bf8bffc7198e
- web https://github.com/ruby/rdoc/commit/d22ba930f1f611dda531dba04cd3d2531bb3f8a5
- web https://github.com/ruby/rdoc/commit/da7a0c7553ef7250ca665a3fecdc01dbaacbb43d
- web https://github.com/ruby/rdoc/commit/e4a0e71e6f1032f8b4e5e58b4ef60d702c22ce17
- web https://hackerone.com/reports/1187477
- web https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rdoc/CVE-2024-27281.yml
- web https://lists.debian.org/debian-lts-announce/2024/09/msg00000.html
- web https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/27LUWREIFTP3MQAW7QE4PJM4DPAQJWXF
- web https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XYDHPHEZI7OQXTQKTDZHGZNPIJH7ZV5N
- web https://www.ruby-lang.org/en/news/2024/03/21/rce-rdoc-cve-2024-27281