CVE-2017-15698

What it is

When parsing the AIA-Extension field of a client certificate, Apache Tomcat Native Connector 1.2.0 to 1.2.14 and 1.1.23 to 1.1.34 did not correctly handle fields longer than 127 bytes. The result of the parsing error was to skip the OCSP check. It was therefore possible for client certificates that should have been rejected (if the OCSP check had been made) to be accepted. Users not using OCSP checks are not affected by this vulnerability.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data tampering.

Exploit odds

3.5% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2018-01-31 14:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:08 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 3.5% in the next 30 days (EPSS).
• Severity: 5.9 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2018-01-31 14:29 UTC

Last modified

2026-06-17 01:08 UTC

Exploit probability

3.5% · EPSS, next 30 days

Weakness

CWE-295 · Improper certificate validation

Record status

Modified

Affected

• Apache Tomcat Native ≤ 1.1.34
• Apache Tomcat Native ≤ 1.2.14
• Debian Linux 8.0
• Debian Linux 9.0

Attack profile CVSS 3.0 · 5.9

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-15698.md and follow it. Check whether this project is affected by CVE-2017-15698. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge