Is CVE-2018-11759 automatically exploitable on my domain?

Not necessarily. ThreatPort treats CVE-2018-11759 as a risk signal that must be connected to observed external assets, detected technologies, and reachable services.

What does ThreatPort check for CVE-2018-11759?

ThreatPort looks for public asset evidence, service fingerprints, CVE-linked technology signals, exposed endpoints, weak DNS/TLS posture, and remediation context.

Should this replace vendor advisories?

No. Use vendor advisories and official patches for final remediation decisions; use ThreatPort to find externally visible exposure and prove cleanup.

CVE-2018-11759 Tomcat Jk Connector exposure check

From CVE Record to External Exposure

The Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map in Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44 did not handle some edge cases correctly. If only a sub-set of the URLs supported by Tomcat were exposed via httpd, then it was possible for a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing the application via the reverse proxy. It was also possible in some configurations for a specially constructed request to bypass the access controls configured in httpd. While there is some overlap between this issue and CVE-2018-1323, they are not identical.

Tomcat Jk Connector vulnerability should be triaged by matching the affected vendor and product to live, internet-facing assets rather than treating the CVE as an abstract feed item. ThreatPort focuses on the first question that budget-constrained IT leaders and CISOs ask: what can an outside observer find today, how severe is it, and what should be fixed first?

Known Exploitation Record

Known ransomware campaign use: Not recorded
EPSS exploitation probability: 90.65% (100p)
CVSS base score: 7.5 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)
Disclosed: 2018-10-31
Weakness type: CWE-22

Source: CISA Known Exploited Vulnerabilities catalog and FIRST.org EPSS.

What ThreatPort Checks

Identify externally reachable services that appear related to Apache Tomcat Jk Connector.

Map detected technologies to CVE-2018-11759, severity context, and practical remediation priority.

Check TLS, DNS, headers, exposed panels, stale endpoints, and service fingerprints from a public attacker perspective.

Produce a concise scorecard first, then unlock deeper AI pentest evidence and PDF reporting when remediation planning begins.

The output is intentionally practical: ownership clues, risk context, remediation hints, and repeatable evidence that can be shared with technical teams or leadership. It is not positioned as magic compliance automation or a replacement for human security judgment.

Lean security teams rarely need another broad vulnerability list. They need to know whether an exposed endpoint, an expired certificate, a weak DNS setting, or a CVE-linked service is likely to affect the systems they actually run. ThreatPort scans from the outside in, ranks what it finds by real reachability rather than raw CVSS, and hands back evidence a team can act on the same day.

Route-Specific Evidence Profile

CVE-2018-11759 affects Apache Tomcat Jk Connector, a CWE-22 weakness. Disclosed 2018-10-31. This page exists to answer one question: is anything you own externally reachable and running it.

Assets This Page Should Care About

Public domains Subdomains Externally reachable web apps TLS endpoints DNS records

Signals Worth Prioritizing

Forgotten subdomains

Weak DNS or email controls

Outdated services

Risky headers

What Should Be Reviewed First in This Context?

For teams running Apache Tomcat Jk Connector, the first step is to validate internet-facing assets with business relevance instead of producing a generic vulnerability list.