CVE-2018-8019
Published: 31 July 2018
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.
Priority
Status
Package | Release | Status |
---|---|---|
tomcat-native Launchpad, Ubuntu, Debian |
bionic |
Not vulnerable
(1.2.17-1)
|
cosmic |
Not vulnerable
(1.2.17-1)
|
|
disco |
Not vulnerable
(1.2.17-1)
|
|
eoan |
Not vulnerable
(1.2.17-1)
|
|
focal |
Not vulnerable
(1.2.17-1)
|
|
groovy |
Not vulnerable
(1.2.17-1)
|
|
hirsute |
Not vulnerable
(1.2.17-1)
|
|
impish |
Not vulnerable
(1.2.17-1)
|
|
jammy |
Not vulnerable
(1.2.17-1)
|
|
kinetic |
Not vulnerable
(1.2.17-1)
|
|
lunar |
Not vulnerable
(1.2.17-1)
|
|
mantic |
Not vulnerable
(1.2.17-1)
|
|
trusty |
Does not exist
(trusty was needs-triage)
|
|
upstream |
Released
(1.2.17-1)
|
|
xenial |
Needed
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.4 |
Attack vector | Network |
Attack complexity | High |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | High |
Availability impact | None |
Vector | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |