Vulnerability in HTTP (CVE-2025-52479)

Summary

Vulnerability in HTTP (CVE-2025-52479). Risk of unauthorized operations or information disclosure. Exploitable via Foo. Mitigation: upgrade to 1.10.17 or later.

Original description

The description as published by the source.

Description

The URIs.jl and HTTP.jl packages allowed the construction of URIs containing CR/LF characters. If user input was not otherwise escaped or protected, this can lead to a CRLF injection attack.

With this simple Julia code, you can inject a custom header named Foo with the value bar:

import HTTP

HTTP.get("http://localhost:1337/ HTTP/1.1\r\nFoo: bar\r\nbaz:")

The server will receive the request like this:

➜ ncat -klp 1337
GET / HTTP/1.1
Foo: bar <-- injected header!
baz: HTTP/1.1
Host: locahost:1337
Accept: */*
User-Agent: HTTP.jl/1.11.5
Content-Length: 0
Accept-Encoding: gzip

Impact

Inject headers or inject data to the request body and cause “HTTP response splitting”.

Patches

Users of HTTP.jl should upgrade immediately to HTTP.jl v1.10.17. All prior versions are vulnerable.

Users of URIs.jl should upgrade immediately to URIs.jl v1.6.0. All prior versions are vulnerable.

The check for valid URIs is now in the URI.jl package, and the latest version of HTTP.jl incorporates that fix.

Workarounds

Manually validate any URIs before passing them on to functions in this package.

References

Fixed by: https://github.com/JuliaWeb/URIs.jl/pull/66 (which is available in URIs.jl v1.6.0).

Credits

Thanks to splitline from the DEVCORE Research Team for reporting this issue.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-2025-52479 has been found in HTTP.
Attackers can target a specific entry point like Foo over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade HTTP to 1.10.17 or later.
If unsure, ask your IT team or search "HTTP CVE-2025-52479" on the vendor's site.

CVE-2025-52479 (HTTP)
Attack surface: Foo / bar
Patched: 1.10.17 — apply immediately
Workaround: Manually validate any URIs before passing them on to functions in this package.
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 (unclassified) exists in HTTP. Attackers reach the vulnerable code path via Foo.

📍 Affected scope

Check the vendor advisory for the affected versions of HTTP. Attack surface: Foo / bar.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.10.17.

🛡️ Workaround

Workaround: Manually validate any URIs before passing them on to functions in this package.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'HTTP' . 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

1
Identify exposure identify
```
grep -r 'HTTP' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で HTTP を grep し、稼働しているサービス・バージョンを把握する。
2
Apply temporary workaround mitigate
```
Manually validate any URIs before passing them on to functions in this package.
```
パッチが適用されるまでの応急処置として、Manually validate any URIs before passing them on to functions in this package. を実施。回避策の副作用 (機能低下) を確認した上で。
3
Apply patch patch
```
Upgrade HTTP to 1.10.17
```
ステージング環境で 1.10.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
4
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Julia HTTP

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.10.17"}]}]

Julia URIs

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.6.0"}]}]