Skip to content
Fencer Vulns
high 7.5

CVE-2017-7675 in the critical feed json

Improper Limitation of a Pathname to a Restricted Directory in Apache Tomcat

published 2017-08-11 9 y ago modified 2026-06-17 4 mo ago also GHSA-68g5-8q7f-m384 , EUVD-2022-2751

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.1%
EPSS 10.1% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.0.M21 and 8.5.0 to 8.5.15 bypassed a number of security checks that prevented directory traversal attacks. It was therefore possible to bypass security constraints using a specially crafted URL.

Patch / fix

  • maven org.apache.tomcat:tomcat 8.5.16, 9.0.0.M22

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-7675 updated cvss 7.5

tomcat: Security Constraint Bypass

  • Red Hat JBoss Enterprise Web Server 3 tomcat8 tomcat8 Red Hat JBoss Fuse 6 tomcat8 tomcat8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

10.14% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.tomcat:tomcat
>=9.0.0.M1, <9.0.0.M22
>=8.5.0, <8.5.16
9.0.0.M22
8.5.16

Affected products

  • Apache Software Foundation Apache Tomcat

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.