Vulnerability in tomcat-native
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 DEBIAN-CVE-2018-8019 has been found in tomcat-native.
Confidential information can be exposed externally.
What to do: upgrade tomcat-native to 1.2.17-1 or later.
If unsure, ask your IT team or search "tomcat-native DEBIAN-CVE-2018-8019" on the vendor's site.
DEBIAN-CVE-2018-8019 (tomcat-native)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.2.17-1 — 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 (unclassified) exists in tomcat-native.
Check the vendor advisory for the affected versions of tomcat-native.
Severity: ?. Confidential information can be exposed externally.
Update to 1.2.17-1.
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. Run grep -r 'tomcat-native' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'tomcat-native' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tomcat-nativeを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade tomcat-native to 1.2.17-1ステージング環境で 1.2.17-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | tomcat-native |
< 1.2.17-1 |
1.2.17-1 |
| Debian:13 | tomcat-native |
< 1.2.17-1 |
1.2.17-1 |
| Debian:14 | tomcat-native |
< 1.2.17-1 |
1.2.17-1 |
Original description The description as published by the source.
When using an OCSP responder Apache Tomcat Native 1.2.0 to 1.2.16 and 1.1.23 to 1.1.34 did not correctly handle invalid responses. This allowed for revoked client certificates to be incorrectly identified. It was therefore possible for users to authenticate with revoked certificates when using mutual TLS. Users not using OCSP checks are not affected by this vulnerability.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org