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.
Original description
The description as published by the source.
A race condition exists in Audited 4.0.0 to 5.3.3 that can result in an authenticated user to cause audit log entries to be attributed to another user.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-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.
A vulnerability (CWE-362) exists in audited. Attackers reach the vulnerable code path via Thread.current.
Check the vendor advisory for the affected versions of audited. Attack surface: Thread.current.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to 5.3.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade audited to 5.3.3ステージング環境で 5.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- report github.com
- report github.com
- report github.com
- web github.com
- web github.com
- web rubygems.org