What is the severity of CVE-2020-13953?

CVE-2020-13953 has a medium severity level as it allows file downloads from the WEB-INF folder, potentially exposing sensitive files.

How do I fix CVE-2020-13953?

To mitigate CVE-2020-13953, upgrade Apache Tapestry to version 5.6.4 or later for versions 5.4.0 to 5.5.0, and for versions 5.7.0 to 5.7.2 upgrade to version 5.7.3 or later.

What versions of Apache Tapestry are affected by CVE-2020-13953?

CVE-2020-13953 affects Apache Tapestry versions 5.4.0 to 5.5.0 and versions 5.7.0 to 5.7.2.

What is the impact of exploiting CVE-2020-13953?

Exploiting CVE-2020-13953 can lead to unauthorized access to sensitive files located in the WEB-INF directory.

Are there any workarounds for CVE-2020-13953?

As a workaround for CVE-2020-13953, restricting URL patterns or implementing necessary access controls can help mitigate the risk until a patch is applied.

Vulnerability/
CVE-2020-13953

medium

5.3

CWE

552

30/9/2020

4/8/2024

CVE-2020-13953

First published: Wed Sep 30 2020(Updated: )

In Apache Tapestry from 5.4.0 to 5.5.0, crafting specific URLs, an attacker can download files inside the WEB-INF folder of the WAR being run.

Credit: security@apache.org

Affected Software	Affected Version	How to fix
Apache Tapestry	>=5.4.0<5.6.4
Apache Tapestry	>=5.7.0<5.7.2

Remedy

https://lists.apache.org/thread.html/r37dab61fc7f7088d4311e7f995ef4117d58d86a675f0256caa6991eb@%3Cusers.tapestry.apache.org%3E

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13953?
CVE-2020-13953 has a medium severity level as it allows file downloads from the WEB-INF folder, potentially exposing sensitive files.
How do I fix CVE-2020-13953?
To mitigate CVE-2020-13953, upgrade Apache Tapestry to version 5.6.4 or later for versions 5.4.0 to 5.5.0, and for versions 5.7.0 to 5.7.2 upgrade to version 5.7.3 or later.
What versions of Apache Tapestry are affected by CVE-2020-13953?
CVE-2020-13953 affects Apache Tapestry versions 5.4.0 to 5.5.0 and versions 5.7.0 to 5.7.2.
What is the impact of exploiting CVE-2020-13953?
Exploiting CVE-2020-13953 can lead to unauthorized access to sensitive files located in the WEB-INF directory.
Are there any workarounds for CVE-2020-13953?
As a workaround for CVE-2020-13953, restricting URL patterns or implementing necessary access controls can help mitigate the risk until a patch is applied.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/last-modified-date
agent/weakness
agent/author
agent/severity
agent/remedy
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/apache
canonical/apache tapestry
version/apache tapestry/5.4.0
version/apache tapestry/5.7.0

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-2020-13953?
CVE-2020-13953 has a medium severity level as it allows file downloads from the WEB-INF folder, potentially exposing sensitive files.
How do I fix CVE-2020-13953?
To mitigate CVE-2020-13953, upgrade Apache Tapestry to version 5.6.4 or later for versions 5.4.0 to 5.5.0, and for versions 5.7.0 to 5.7.2 upgrade to version 5.7.3 or later.
What versions of Apache Tapestry are affected by CVE-2020-13953?
CVE-2020-13953 affects Apache Tapestry versions 5.4.0 to 5.5.0 and versions 5.7.0 to 5.7.2.
What is the impact of exploiting CVE-2020-13953?
Exploiting CVE-2020-13953 can lead to unauthorized access to sensitive files located in the WEB-INF directory.
Are there any workarounds for CVE-2020-13953?
As a workaround for CVE-2020-13953, restricting URL patterns or implementing necessary access controls can help mitigate the risk until a patch is applied.