← Back
CVE-2024-22047
low
CVSS 3.1
Vulnerability in audited (CVE-2024-22047)
Summary
vulnerability in audited (CVE-2024-22047). Risk of unauthorized operations or information disclosure. Exploitable via ``Thread.current``. Mitigation: upgrade to `5.3.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-22047** has been found in audited.
Attackers can target a specific entry point like ``Thread.current`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade audited to **5.3.3** or later.
If unsure, ask your IT team or search "audited CVE-2024-22047" on the vendor's site.
CVE-2024-22047 (audited) — CWE-362 / CVSS v3 3.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `Thread.current`
Patched: `5.3.3` — 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
**A vulnerability** (CWE-362) exists in audited. Attackers reach the vulnerable code path via ``Thread.current`` without authentication.
📍 Affected scope
audited — . Attack surface: `Thread.current`.
🔥 Severity
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.3.3**.
🛡️ 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 'audited' .` 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 'audited' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `audited` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade audited to 5.3.3ステージング環境で 5.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
RubyGems
audited
[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"5.3.3"}]}]
References
- advisory af854a3a-2127-422b-91ae-364da2661108
- web https://github.com/collectiveidea/audited/issues/601
- web https://github.com/collectiveidea/audited/pull/669
- web https://github.com/collectiveidea/audited/pull/671
- web https://github.com/collectiveidea/audited/security/advisories/GHSA-hjp3-5g2q-7jww
- advisory af854a3a-2127-422b-91ae-364da2661108
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-22047
- web https://github.com/collectiveidea/audited/commit/342734c9396d8f96d3165f1d8531c626139fa4c6
- package https://github.com/collectiveidea/audited
- web https://github.com/rubysec/ruby-advisory-db/blob/master/gems/audited/CVE-2024-22047.yml