Path Traversal in com.linecorp.armeria:armeria (CVE-2021-43795)
Summary
Path traversal in com.linecorp.armeria:armeria (CVE-2021-43795). Confidential information can be exposed externally. Mitigation: upgrade to 1.13.4 or later.
Original description
The description as published by the source.
Armeria is an open source microservice framework. In affected versions an attacker can access an Armeria server's local file system beyond its restricted directory by sending an HTTP request whose path contains %2F (encoded /), such as /files/..%2Fsecrets.txt, bypassing Armeria's path validation logic. Armeria 1.13.4 or above contains the hardened path validation logic that handles %2F properly. This vulnerability can be worked around by inserting a decorator that performs an additional validation on the request path.
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-43795 has been found in com.linecorp.armeria:armeria.
Confidential information can be exposed externally.
What to do: upgrade com.linecorp.armeria:armeria to 1.13.4 or later.
If unsure, ask your IT team or search "com.linecorp.armeria:armeria CVE-2021-43795" on the vendor's site.
CVE-2021-43795 (com.linecorp.armeria:armeria) — CWE-22
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.13.4 — 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.
Path traversal (CWE-22) exists in com.linecorp.armeria:armeria.
Check the vendor advisory for the affected versions of com.linecorp.armeria:armeria.
Severity: ?. Confidential information can be exposed externally.
Update to 1.13.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.linecorp.armeria:armeria を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.linecorp.armeria:armeria to 1.13.4ステージング環境で 1.13.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com