Vulnerability in httparty (CVE-2024-22049)
Summary
Vulnerability in httparty (CVE-2024-22049). Data can be tampered with by attackers. Exploitable via body.rb. Mitigation: upgrade to 0.21.0 or later.
Original description
The description as published by the source.
httparty before 0.21.0 is vulnerable to an assumed-immutable web parameter vulnerability. A remote and unauthenticated attacker can provide a crafted filename parameter during multipart/form-data uploads which could result in attacker controlled filenames being written.
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-22049 has been found in httparty.
Attackers can target a specific entry point like body.rb over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.3/10.
What to do: upgrade httparty to 0.21.0 or later.
If unsure, ask your IT team or search "httparty CVE-2024-22049" on the vendor's site.
CVE-2024-22049 (httparty) — CWE-472 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: body.rb / abc.txt / avatar / foo
Patched: 0.21.0 — 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-472) exists in httparty. Attackers reach the vulnerable code path via body.rb without authentication.
Check the vendor advisory for the affected versions of httparty. Attack surface: body.rb / abc.txt / avatar / foo.
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers.
Update to 0.21.0.
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 'httparty' . 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 'httparty' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
httpartyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade httparty to 0.21.0ステージング環境で 0.21.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2024-22049 ruby-httparty Fixed in: 0.18.1-2+deb11u1
References
- advisory github.com
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web lists.debian.org
- web lists.fedoraproject.org
- web lists.fedoraproject.org
- web lists.debian.org
- web github.com
- web rubygems.org