What is the severity of CVE-2001-0917?

CVE-2001-0917 has a medium severity level as it allows remote attackers to access sensitive information.

How do I fix CVE-2001-0917?

To fix CVE-2001-0917, upgrade to a later version of Apache Tomcat that addresses this vulnerability.

What type of information can be exposed by CVE-2001-0917?

CVE-2001-0917 can expose physical path information of the server, which can assist attackers in further exploits.

Which versions of Tomcat are affected by CVE-2001-0917?

CVE-2001-0917 specifically affects Jakarta Tomcat version 4.0.1.

Is there a workaround for CVE-2001-0917?

A potential workaround for CVE-2001-0917 is to avoid using long URLs with .JSP extensions in your application.

Vulnerability/
CVE-2001-0917

medium

CWE

NVD-CWE-Other

22/11/2001

25/6/2002

8/8/2024

CVE-2001-0917

First published: Thu Nov 22 2001(Updated: )

Jakarta Tomcat 4.0.1 allows remote attackers to reveal physical path information by requesting a long URL with a .JSP extension.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Apache Tomcat	=4.0.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2001-0917?
CVE-2001-0917 has a medium severity level as it allows remote attackers to access sensitive information.
How do I fix CVE-2001-0917?
To fix CVE-2001-0917, upgrade to a later version of Apache Tomcat that addresses this vulnerability.
What type of information can be exposed by CVE-2001-0917?
CVE-2001-0917 can expose physical path information of the server, which can assist attackers in further exploits.
Which versions of Tomcat are affected by CVE-2001-0917?
CVE-2001-0917 specifically affects Jakarta Tomcat version 4.0.1.
Is there a workaround for CVE-2001-0917?
A potential workaround for CVE-2001-0917 is to avoid using long URLs with .JSP extensions in your application.

collector/nvd-historical
collector/nvd-index
collector/nvd-api
agent/type
agent/author
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/references
agent/weakness
agent/last-modified-date
agent/severity
agent/tags
agent/event
agent/description
agent/source
vendor/apache
canonical/apache tomcat
version/apache tomcat/4.0.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2001-0917?
CVE-2001-0917 has a medium severity level as it allows remote attackers to access sensitive information.
How do I fix CVE-2001-0917?
To fix CVE-2001-0917, upgrade to a later version of Apache Tomcat that addresses this vulnerability.
What type of information can be exposed by CVE-2001-0917?
CVE-2001-0917 can expose physical path information of the server, which can assist attackers in further exploits.
Which versions of Tomcat are affected by CVE-2001-0917?
CVE-2001-0917 specifically affects Jakarta Tomcat version 4.0.1.
Is there a workaround for CVE-2001-0917?
A potential workaround for CVE-2001-0917 is to avoid using long URLs with .JSP extensions in your application.