Skip to content
Noroxi
CVE-2018-11759· NVD / CVE Program· CNA apache

The Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map in Apache Tomcat JK

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.

HighCVSS 7.5 · v3.0—Proof of concept Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Oct 31, 2018
Updated
Jun 16, 2026
EPSS
90.6% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

57

Plan

Add it to your regular patch cycle.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
27 / 30 · 90.6%

Affected systems

VendorProduct
apachetomcat jk connector
debiandebian linux
redhatjboss core services

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache tomcat jk connector1.2.0 and later · up to 1.2.44 inclusive
  • debian debian linux8.0
  • debian debian linux9.0
  • redhat jboss core servicesall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Tomcat Connectors

    • Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12libapache-mod-jkbefore 1:1.2.46-11:1.2.46-1
Debian:8libapache-mod-jkbefore 1:1.2.46-0+deb8u11:1.2.46-0+deb8u1
Debian:9libapache-mod-jkbefore 1:1.2.46-0+deb9u11:1.2.46-0+deb9u1
openSUSE:Tumbleweedapache2-mod_jkbefore 1.2.48-2.91.2.48-2.9
Red Hat:jboss_core_services:1::el6jbcs-httpd24before 0:1-6.jbcs.el60:1-6.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apache-commons-daemon-jsvcbefore 1:1.1.0-3.redhat_2.jbcs.el61:1.1.0-3.redhat_2.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apache-commons-daemon-jsvc-debuginfobefore 1:1.1.0-3.redhat_2.jbcs.el61:1.1.0-3.redhat_2.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-aprbefore 0:1.6.3-31.jbcs.el60:1.6.3-31.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-debuginfobefore 0:1.6.3-31.jbcs.el60:1.6.3-31.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-develbefore 0:1.6.3-31.jbcs.el60:1.6.3-31.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-utilbefore 0:1.6.1-24.jbcs.el60:1.6.1-24.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-debuginfobefore 0:1.6.1-24.jbcs.el60:1.6.1-24.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-develbefore 0:1.6.1-24.jbcs.el60:1.6.1-24.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-ldapbefore 0:1.6.1-24.jbcs.el60:1.6.1-24.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-mysqlbefore 0:1.6.1-24.jbcs.el60:1.6.1-24.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-nssbefore 0:1.6.1-24.jbcs.el60:1.6.1-24.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-odbcbefore 0:1.6.1-24.jbcs.el60:1.6.1-24.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-opensslbefore 0:1.6.1-24.jbcs.el60:1.6.1-24.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-pgsqlbefore 0:1.6.1-24.jbcs.el60:1.6.1-24.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-sqlitebefore 0:1.6.1-24.jbcs.el60:1.6.1-24.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-httpdbefore 0:2.4.29-35.jbcs.el60:2.4.29-35.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-httpd-debuginfobefore 0:2.4.29-35.jbcs.el60:2.4.29-35.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-httpd-develbefore 0:2.4.29-35.jbcs.el60:2.4.29-35.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-httpd-manualbefore 0:2.4.29-35.jbcs.el60:2.4.29-35.jbcs.el6

+69

Other highest-scoring records for the same primary product.

  • CVE-2016-6808Buffer overflow in Apache Tomcat Connectors (mod_jk) before 1.2.42.
    46Plan
  • CVE-2018-1323The IIS/ISAPI specific code in the Apache Tomcat JK ISAPI Connector 1.2.0 to 1.2.42 that normalised the requested path before matching it to
    44Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:libapache-mod-jk1:1.2.46-1 · Debian:12Package registry (OSV)
opensuse:apache2-mod_jk1.2.49-150100.6.6.1 · openSUSE:Leap 15.4Package registry (OSV)
red hat:jbcs-httpd240:1-6.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apache-commons-daemon-jsvc1:1.1.0-3.redhat_2.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apache-commons-daemon-jsvc-debuginfo1:1.1.0-3.redhat_2.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apr0:1.6.3-31.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apr-debuginfo0:1.6.3-31.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apr-devel0:1.6.3-31.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apr-util0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apr-util-debuginfo0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apr-util-devel0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apr-util-ldap0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apr-util-mysql0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
red hat:jbcs-httpd24-apr-util-nss0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6Package registry (OSV)
suse:apache2-mod_jk1.2.40-7.3.1 · SUSE:Linux Enterprise Server 12 SP4Package registry (OSV)
suse:apache2-mod_jk1.2.49-150100.6.6.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP4Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Nuclei detection templateNuclei template CVE-2018-11759 —
Proof-of-concept repository on GitHubstars:392018-11-01
Proof-of-concept repository on GitHubstars:52018-12-08
Proof-of-concept repository on GitHubstars:02024-04-18

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoCsame day
  3. TodaySep 30, 2026+2891 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records