← Back
GHSA-387m-935m-c4vw
Vulnerability in io.micronaut:micronaut-http-client (GHSA-387m-935m-c4vw)
Summary
vulnerability in io.micronaut:micronaut-http-client (GHSA-387m-935m-c4vw). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `5.0.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-387m-935m-c4vw** has been found in io.micronaut:micronaut-http-client.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade io.micronaut:micronaut-http-client to **5.0.1** or later.
If unsure, ask your IT team or search "io.micronaut:micronaut-http-client GHSA-387m-935m-c4vw" on the vendor's site.
GHSA-387m-935m-c4vw (io.micronaut:micronaut-http-client) —
Patched: `5.0.1` — 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** (unclassified) exists in io.micronaut:micronaut-http-client.
📍 Affected scope
io.micronaut:micronaut-http-client — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.0.1**.
🛡️ 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 'io.micronaut:micronaut-http-client' .` 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 'io.micronaut:micronaut-http-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.micronaut:micronaut-http-client` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.micronaut:micronaut-http-client to 5.0.1ステージング環境で 5.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.micronaut:micronaut-http-client
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.1"}]}]
References
- web https://github.com/micronaut-projects/micronaut-core/security/advisories/GHSA-387m-935m-c4vw
- web https://github.com/micronaut-projects/micronaut-core/commit/6e88a972718d6e1521c5b3bb7766451798dba4e3
- web https://github.com/micronaut-projects/micronaut-core/commit/c06a2715ca7f78321bc3ca05f41cca78cd351320
- web https://github.com/micronaut-projects/micronaut-core/commit/f1dffffec8fb5e3b7e94ae907ce0be3831e499d4
- web https://github.com/advisories/GHSA-387m-935m-c4vw