← Back
CVE-2025-68696
SSRF (Server-Side Request Forgery) in httparty (CVE-2025-68696)
Summary
SSRF in httparty (CVE-2025-68696). Confidential information can be exposed externally. Exploitable via `POST /issue`. Mitigation: upgrade to `0.24.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-68696** has been found in httparty.
Attackers can target a specific entry point like `POST /issue` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade httparty to **0.24.0** or later.
If unsure, ask your IT team or search "httparty CVE-2025-68696" on the vendor's site.
CVE-2025-68696 (httparty) — CWE-918 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /issue / `base_uri` / `urljoin` / `main.rb`
Patched: `0.24.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.
❓ What is the problem
**SSRF** (CWE-918) exists in httparty. Attackers reach the vulnerable code path via `POST /issue` without authentication.
📍 Affected scope
httparty — . Attack surface: POST /issue / `base_uri` / `urljoin` / `main.rb`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **0.24.0**.
🛡️ 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 `POST /issue` requests with malformed payloads or SQL meta-characters. Run `grep -r 'httparty' .` 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 'httparty' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `httparty` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /issue' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /issue` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade httparty to 0.24.0ステージング環境で 0.24.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /issue on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
RubyGems
httparty
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.24.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-68696
- package https://github.com/jnunemaker/httparty
- web https://github.com/jnunemaker/httparty/security/advisories/GHSA-hm5p-x4rq-38w4
- web https://github.com/jnunemaker/httparty/commit/0529bcd6309c9fd9bfdd50ae211843b10054c240
- web https://github.com/rubysec/ruby-advisory-db/blob/master/gems/httparty/CVE-2025-68696.yml