Sign in Sign up
JA · EN · FR
SecPulse
← Back
GHSA-m4w9-hjfw-vwj4

Vulnerability in org.http4k:http4k-core (GHSA-m4w9-hjfw-vwj4)

Summary

vulnerability in org.http4k:http4k-core (GHSA-m4w9-hjfw-vwj4). Risk of unauthorized operations or information disclosure. Exploitable via ``HmacSha256``. Mitigation: upgrade to `6.49.0.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **GHSA-m4w9-hjfw-vwj4** has been found in org.http4k:http4k-core. Attackers can target a specific entry point like ``HmacSha256`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade org.http4k:http4k-core to **6.49.0.0** or later. If unsure, ask your IT team or search "org.http4k:http4k-core GHSA-m4w9-hjfw-vwj4" on the vendor's site.
GHSA-m4w9-hjfw-vwj4 (org.http4k:http4k-core) — CWE-345 / Attack surface: `HmacSha256` / `Hmac` / `HmacSha256.hash` / `AwsSignatureV4Signer.kt` Patched: `6.49.0.0` — apply immediately Workaround: If you cannot upgrade and you need a real HMAC-SHA256, use `javax.crypto.Mac.getInstance("HmacSHA256")` with a `SecretKeySpec`. 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** (CWE-345) exists in org.http4k:http4k-core. Attackers reach the vulnerable code path via ``HmacSha256`` without authentication.
📍 Affected scope
org.http4k:http4k-core — . Attack surface: `HmacSha256` / `Hmac` / `HmacSha256.hash` / `AwsSignatureV4Signer.kt`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.49.0.0**.
🛡️ Workaround
Workaround: If you cannot upgrade and you need a real HMAC-SHA256, use `javax.crypto.Mac.getInstance("HmacSHA256")` with a `SecretKeySpec`.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.http4k:http4k-core' .` 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

  1. 1
    Identify exposure identify 
    grep -r 'org.http4k:http4k-core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.http4k:http4k-core` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate 
    If you cannot upgrade and you need a real HMAC-SHA256, use `javax.crypto.Mac.getInstance("HmacSHA256")` with a `SecretKeySpec`.

    パッチが適用されるまでの応急処置として、If you cannot upgrade and you need a real HMAC-SHA256, use `javax.crypto.Mac.getInstance("HmacSHA256")` with a `SecretKeySpec`. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade org.http4k:http4k-core to 6.49.0.0

    ステージング環境で 6.49.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.http4k:http4k-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.49.0.0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →