Categories
CVE-2021-32769

Path Traversal in io.micronaut:micronaut-http-server-netty (CVE-2021-32769)

Summary

Path traversal in io.micronaut:micronaut-http-server-netty (CVE-2021-32769). Confidential information can be exposed externally. Mitigation: upgrade to 2.5.9 or later.

Original description

The description as published by the source.

Micronaut is a JVM-based, full stack Java framework designed for building JVM applications. A path traversal vulnerability exists in versions prior to 2.5.9. With a basic configuration, it is possible to access any file from a filesystem, using "/../../" in the URL. This occurs because Micronaut does not restrict file access to configured paths. The vulnerability is patched in version 2.5.9. As a workaround, do not use ** in mapping, use only *, which exposes only flat structure of a directory not allowing traversal. If using Linux, another workaround is to run micronaut in chroot.

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-2021-32769 has been found in io.micronaut:micronaut-http-server-netty.
Confidential information can be exposed externally.
What to do: upgrade io.micronaut:micronaut-http-server-netty to 2.5.9 or later.
If unsure, ask your IT team or search "io.micronaut:micronaut-http-server-netty CVE-2021-32769" on the vendor's site.

CVE-2021-32769 (io.micronaut:micronaut-http-server-netty) — CWE-22
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.5.9 — 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

Path traversal (CWE-22) exists in io.micronaut:micronaut-http-server-netty.

📍 Affected scope

Check the vendor advisory for the affected versions of io.micronaut:micronaut-http-server-netty.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 2.5.9.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.micronaut:micronaut-http-server-netty を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade io.micronaut:micronaut-http-server-netty to 2.5.9

    ステージング環境で 2.5.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

Maven io.micronaut:micronaut-http-server-netty
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.5.9"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details