Skip to content
Noroxi
NVD / CVE Program· CNA apache

CVE-2017-5664: The error page mechanism of the Java Servlet Specification requires that, when an error occurs and an error page is configured for the error…

HighCVSS 7.5 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 16.5% (FIRST EPSS); higher than 97% of all records.
  • 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.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: tomcat7 (Debian:7) 7.0.28-4+deb7u14; tomcat7 (Debian:8) 7.0.56-3+deb8u11; tomcat8 (Debian:8) 8.0.14-1+deb8u10.

Low priority for now. Upgrade to tomcat7 (Debian:7) 7.0.28-4+deb7u14; tomcat7 (Debian:8) 7.0.56-3+deb8u11; tomcat8 (Debian:8) 8.0.14-1+deb8u10 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The error page mechanism of the Java Servlet Specification requires that, when an error occurs and an error page is configured for the error that occurred, the original request and response are forwarded to the error page. This means that the request is presented to the error page with the original HTTP method. If the error page is a static file, expected behaviour is to serve content of the file as if processing a GET request, regardless of the actual HTTP method. The Default Servlet in Apache Tomcat 9.0.0.M1 to 9.0.0.M20, 8.5.0 to 8.5.14, 8.0.0.RC1 to 8.0.43 and 7.0.0 to 7.0.77 did not do this. Depending on the original request this could lead to unexpected and undesirable results for static error pages including, if the DefaultServlet is configured to permit writes, the replacement or removal of the custom error page. Notes for other user provided error pages: (1) Unless explicitly coded otherwise, JSPs ignore the HTTP method. JSPs used as error pages must must ensure that they handle any error dispatch as a GET request, regardless of the actual method. (2) By default, the response generated by a Servlet does depend on the HTTP method. Custom Servlets used as error pages must ensure that they handle any error dispatch as a GET request, regardless of the actual method.

Published
Jun 6, 2017
Updated
Oct 15, 2026
EPSS
16.5% · 97th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

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

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2017-5664

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apachetomcat

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

    • 9.0.0.M1 to 9.0.0.M20, 8.5.0 to 8.5.14, 8.0.0.RC1 to 8.0.43, 7.0.0 to 7.0.77affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:7tomcat7before 7.0.28-4+deb7u147.0.28-4+deb7u14
Debian:8tomcat7before 7.0.56-3+deb8u117.0.56-3+deb8u11
Debian:8tomcat8before 8.0.14-1+deb8u108.0.14-1+deb8u10
Debian:9tomcat8before 8.5.14-1+deb9u18.5.14-1+deb9u1
Mavenorg.apache.tomcat:tomcatfrom 7.0.0 · before 7.0.787.0.78
Mavenorg.apache.tomcat:tomcatfrom 8.0.0 · before 8.0.448.0.44
Mavenorg.apache.tomcat:tomcatfrom 8.5.0 · before 8.5.158.5.15
Mavenorg.apache.tomcat:tomcatfrom 9.0.0.M1 · before 9.0.0.M219.0.0.M21
openSUSE:Tumbleweedtomcatbefore 9.0.36-8.49.0.36-8.4
openSUSE:Tumbleweedtomcat10before 10.1.14-1.110.1.14-1.1
Red Hat:enterprise_linux:6::clienttomcat6before 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-admin-webappsbefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-docs-webappbefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-el-2.1-apibefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-javadocbefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-jsp-2.1-apibefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-libbefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-servlet-2.5-apibefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-webappsbefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:7::clienttomcatbefore 0:7.0.69-12.el7_30:7.0.69-12.el7_3
Red Hat:enterprise_linux:7::clienttomcat-admin-webappsbefore 0:7.0.69-12.el7_30:7.0.69-12.el7_3
Red Hat:enterprise_linux:7::clienttomcat-docs-webappbefore 0:7.0.69-12.el7_30:7.0.69-12.el7_3
Red Hat:enterprise_linux:7::clienttomcat-el-2.2-apibefore 0:7.0.69-12.el7_30:7.0.69-12.el7_3
Red Hat:enterprise_linux:7::clienttomcat-javadocbefore 0:7.0.69-12.el7_30:7.0.69-12.el7_3

+96

Other highest-scoring records for the same primary product.

  • CVE-2025-24813Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUTKEV
    99Now
  • CVE-2016-8735Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x…KEV
    96Now
  • CVE-2017-12617When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g.KEV
    92Now

Published before and after this one in the same product

  • ← EarlierCVE-2017-5647Apr 17, 2017 · A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to…
    35Monitor
  • ← EarlierCVE-2017-5648Apr 17, 2017 · While investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.
    40Plan
  • Later →CVE-2016-0762Aug 10, 2017 · The Realm implementations in Apache Tomcat versions 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to…
    25Monitor

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:tomcat77.0.28-4+deb7u14 · Debian:7Package registry (OSV)
debian:tomcat88.0.14-1+deb8u10 · Debian:8Package registry (OSV)
Maven:org.apache.tomcat:tomcat7.0.78Package registry (OSV)
Maven:org.apache.tomcat:tomcat8.0.44Package registry (OSV)
Maven:org.apache.tomcat:tomcat8.5.15Package registry (OSV)
Maven:org.apache.tomcat:tomcat9.0.0.M21Package registry (OSV)
opensuse:tomcat9.0.36-8.4 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:tomcat1010.1.14-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:log4j-eap60:1.2.16-12.redhat_3.1.ep6.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat-native0:1.2.8-10.redhat_10.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat-native-debuginfo0:1.2.8-10.redhat_10.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat70:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-admin-webapps0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-docs-webapp0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-el-2.2-api0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-javadoc0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-jsp-2.2-api0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-jsvc0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-lib0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-log4j0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
suse:tomcat8.0.43-29.5.1 · SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2Package registry (OSV)
suse:tomcat66.0.53-0.57.7.1 · SUSE:Linux Enterprise Server 11 SP4Package 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records