XXE (XML External Entity) in com.puppycrawl.tools:checkstyle (CVE-2019-10782)
Summary
Vulnerability in com.puppycrawl.tools:checkstyle (CVE-2019-10782). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.29 or later.
Original description
The description as published by the source.
Due to an incomplete fix for CVE-2019-9658, checkstyle was still vulnerable to XML External Entity (XXE) Processing.
Impact
User: Build Maintainers
This vulnerability probably doesn't impact Maven/Gradle users as, in most cases, these builds are processing files that are trusted, or pre-vetted by a pull request reviewer before being run on internal CI infrastructure.
User: Static Analysis as a Service
If you operate a site/service that parses "untrusted" Checkstyle XML configuration files, you are vulnerable to this and should patch.
Note from the discoverer of the original CVE-2019-9658:
While looking at a few companies that run Checkstyle/PMD/ect... as a service I notice that it's a common pattern to run the static code analysis tool inside of a Docker container with the following flags:
--net=none \ --privileged=false \ --cap-drop=ALLRunning the analysis in Docker has the advantage that there should be no sensitive local file information that XXE can exfiltrate from the container. Additionally, these flags prevent vulnerabilities in static analysis tools like Checkstyle from being used to exfiltrate data via XXE or to perform SSRF.
- Jonathan Leitschuh
Patches
Has the problem been patched? What versions should users upgrade to?
Patched, will be released with version 8.29 at 26 Jan 2020.
Workarounds
_Is there a way fo…
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-2019-10782 has been found in com.puppycrawl.tools:checkstyle.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.puppycrawl.tools:checkstyle to 8.29 or later.
If unsure, ask your IT team or search "com.puppycrawl.tools:checkstyle CVE-2019-10782" on the vendor's site.
CVE-2019-10782 (com.puppycrawl.tools:checkstyle) — CWE-611
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.29 — 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-611) exists in com.puppycrawl.tools:checkstyle.
Check the vendor advisory for the affected versions of com.puppycrawl.tools:checkstyle.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 8.29.
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.puppycrawl.tools:checkstyle を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.puppycrawl.tools:checkstyle to 8.29ステージング環境で 8.29 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web lists.apache.org
- web lists.debian.org
- web snyk.io