Skip to content
Noroxi
CVE-2018-1048· NVD / CVE Program· CNA redhat

It was found that the AJP connector in undertow, as shipped in Jboss EAP 7.1.0.GA, does not use the ALLOW_ENCODED_SLASH option and thus allo

It was found that the AJP connector in undertow, as shipped in Jboss EAP 7.1.0.GA, does not use the ALLOW_ENCODED_SLASH option and thus allow the the slash / anti-slash characters encoded in the url which may lead to path traversal and result in the information disclosure of arbitrary local files.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Jan 24, 2018
Updated
Jun 16, 2026
EPSS
1.6% · 75th 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

30

Monitor

Low priority for now.

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

Affected systems

VendorProduct
redhatjboss enterprise application platform

Affected versions

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

  • redhat jboss enterprise application platform7.1.0

Versions reported by the vendor

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

  • Red Hat, Inc. undertow as shipped in Jboss EAP 7.1.0.GA

    • 7.1.0.GAaffected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:14undertowbefore 1.4.22-11.4.22-1
Mavenorg.jboss.eap:wildfly-undertowfrom 7.1.0.GA · before 7.1.1.GA7.1.1.GA
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemisbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-clibefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-commonsbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-core-clientbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-dtobefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-hornetq-protocolbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-hqclient-protocolbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-jdbc-storebefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-jms-clientbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-jms-serverbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-journalbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-nativebefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-rabefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-selectorbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-serverbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-activemq-artemis-service-extensionsbefore 0:1.5.5.009-1.redhat_1.1.ep7.el60:1.5.5.009-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-apache-cxfbefore 0:3.1.13-1.redhat_1.1.ep7.el60:3.1.13-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-apache-cxf-rtbefore 0:3.1.13-1.redhat_1.1.ep7.el60:3.1.13-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-apache-cxf-servicesbefore 0:3.1.13-1.redhat_1.1.ep7.el60:3.1.13-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-apache-cxf-toolsbefore 0:3.1.13-1.redhat_1.1.ep7.el60:3.1.13-1.redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-glassfish-jsfbefore 0:2.2.13-6.SP5_redhat_1.1.ep7.el60:2.2.13-6.SP5_redhat_1.1.ep7.el6
Red Hat:jboss_enterprise_application_platform:7::el6eap7-hibernatebefore 0:5.1.12-1.Final_redhat_1.1.ep7.el60:5.1.12-1.Final_redhat_1.1.ep7.el6

+96

Other highest-scoring records for the same primary product.

  • CVE-2017-12149In Jboss Application Server as shipped with Red Hat Enterprise Application Platform 5.2, it was found that the doFilter method in the ReadOnKEV
    96Now
  • CVE-2010-1871JBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, does not properly sanitize inputs for KEV
    90Now
  • CVE-2010-1428The Web Console (aka web-console) in JBossAs in Red Hat JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.2 before 4.2.0.CP09KEV
    79This week
  • CVE-2010-0738The JMX-Console web application in JBossAs in Red Hat JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.2 before 4.2.0.CP09 aKEV
    75This week
  • CVE-2016-2183The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of appr
    58Plan
  • CVE-2017-7504HTTPServerILServlet.java in JMS over HTTP Invocation Layer of the JbossMQ implementation, which is enabled by default in Red Hat Jboss Appli
    51Plan

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:undertow1.4.22-1 · Debian:14Package registry (OSV)
Maven:org.jboss.eap:wildfly-undertow7.1.1.GAPackage registry (OSV)
red hat:eap7-activemq-artemis0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-cli0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-commons0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-core-client0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-dto0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-hornetq-protocol0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-hqclient-protocol0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-jdbc-store0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-jms-client0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-jms-server0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-journal0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)
red hat:eap7-activemq-artemis-native0:1.5.5.009-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

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.1/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);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; 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

Change log

  1. Fix✗ → ✓

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

References

All records