Vulnerability in io.dropwizard:dropwizard-validation (CVE-2020-5245)
Summary
Vulnerability in io.dropwizard:dropwizard-validation (CVE-2020-5245). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.0.2 or later.
Original description
The description as published by the source.
Dropwizard-Validation before 1.3.19, and 2.0.2 may allow arbitrary code execution on the host system, with the privileges of the Dropwizard service account, by injecting arbitrary Java Expression Language expressions when using the self-validating feature.
The issue has been fixed in dropwizard-validation 1.3.19 and 2.0.2.
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-2020-5245 has been found in io.dropwizard:dropwizard-validation.
Successful exploitation can lead to full system takeover.
What to do: upgrade io.dropwizard:dropwizard-validation to 2.0.2 or later.
If unsure, ask your IT team or search "io.dropwizard:dropwizard-validation CVE-2020-5245" on the vendor's site.
CVE-2020-5245 (io.dropwizard:dropwizard-validation) — CWE-74
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.0.2 — 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.
A vulnerability (CWE-74) exists in io.dropwizard:dropwizard-validation.
Check the vendor advisory for the affected versions of io.dropwizard:dropwizard-validation.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.0.2.
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・依存マニフェストで io.dropwizard:dropwizard-validation を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.dropwizard:dropwizard-validation to 2.0.2ステージング環境で 2.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory beanvalidation.org
- advisory docs.jboss.org
- advisory docs.oracle.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- report github.com
- web oracle.com