Patchfirst
CVE-2008-2938 Public exploit EPSS 99.7%

Directory traversal vulnerability in Apache Tomcat 4.1.0 through 4.1.37, 5.5.0 through 5.5.26, and 6.0.0 through…

Summary

Apache Tomcat versions 4.1.0 through 4.1.37, 5.5.0 through 5.5.26, and 6.0.0 through 6.0.16 contain a directory traversal flaw in the handling of request URIs. An unauthenticated remote attacker can read arbitrary files on the server by sending encoded directory traversal sequences in the URI, provided that allowLinking and UTF-8 are enabled in the configuration.

Official description · CVE.org

Directory traversal vulnerability in Apache Tomcat 4.1.0 through 4.1.37, 5.5.0 through 5.5.26, and 6.0.0 through 6.0.16, when allowLinking and UTF-8 are enabled, allows remote attackers to read arbitrary files via encoded directory traversal sequences in the URI, a different vulnerability than CVE-2008-2370. NOTE: versions earlier than 6.0.18 were reported affected, but the vendor advisory lists 6.0.16 as the last affected version.

Breakdown
27.7 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15

Public exploit code (Exploit-DB) was available 2 days before disclosure.

  1. Public exploit codeExploit-DB2 days before
  2. Disclosedday 0

See the family tree

A fix was bypassed or incomplete once over 9 years. The latest fix listed for tomcat is 6.0.20.

Same bug familyLinked by evidence that a fix failed or the same code was patched again. Oldest first.

  1. CVE-2005-2090Jakarta Tomcat 5.0.19 (Coyote/1.1) and Tomcat 4.1.24…30 Jun 2005
  2. same family
    This CVECVE-2008-2938Directory traversal vulnerability in Apache Tomcat 4.1.0 through…13 Aug 2008
  3. same family
    CVE-2010-2227Tomcat 5.5.0 through 5.5.29, 6.0.0 through 6.0.27, and 7.0.0…13 Jul 2010
  4. same family
    CVE-2011-3190Certain AJP protocol connector implementations in Apache Tomcat…31 Aug 2011
  5. relatedHigh

    Why these are linked:

    • Fixed one release later7.0.21 → 7.0.22 (org.apache.tomcat:tomcat)
    • Same code patched: AbstractAjpProcessor.java, AjpAprProcessor.java, AjpNioProcessor.java, AjpProcessor.java (machine-matched)Functions: processcommit a2538cecommit 9eae334
    CVE-2011-3375Tomcat 6.0.30 through 6.0.33 and 7.x before 7.0.22 does not…19 Jan 2012
  6. relatedMedium

    Why these are linked:

    CVE-2013-4286Tomcat before 6.0.39, 7.x before 7.0.47, and 8.x before…26 Feb 2014

Fixes in tomcatMaven package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 6.0.17CVE-2008-12324 Aug 2008
  2. 6.0.18CVE-2008-19474 Jun 2008
  3. 6.0.18CVE-2008-23704 Aug 2008
  4. 6.0.18CVE-2008-293813 Aug 2008
  5. 6.0.19CVE-2009-05805 Jun 2009
  6. 6.0.20CVE-2009-07819 Mar 2009
  7. 6.0.20CVE-2008-551516 Jun 2009Latest listed

techniques

No techniques linked

No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: org.apache.tomcat:tomcat.

Mavenorg.apache.tomcat:tomcatGHSA-m7xj-ccqc-p4g2

Upgrade to 6.0.35 or later

Fixes this CVE and 8 other known vulnerabilities in this package (CVE-2007-0450, CVE-2007-2449, +6).

Set the version to 6.0.35 or later in your pom.xml or build.gradle.

First fixed in 6.0.18 for CVE-2008-2938.

Affected versions, by release line

If you runUpgrade to
6.0.0 up to 6.0.186.0.35first fix for this CVE: 6.0.18
5.5.0 up to 5.5.275.5.35first fix for this CVE: 5.5.27
4.1.0 up to 4.1.394.1.40first fix for this CVE: 4.1.39

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

Also mentioned in 15 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

43 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close