About vulnerability

Description

Spring Framework MVC applications can be vulnerable to a “Path Traversal Vulnerability” when deployed on a non-compliant Servlet container.

An application can be vulnerable when all the following are true:

• the application is deployed as a WAR or with an embedded Servlet container
• the Servlet container does not reject suspicious sequences
• the application serves static resources with Spring resource handling

We have verified that applications deployed on Apache Tomcat or Eclipse Jetty are not vulnerable, as long as default security features are not disabled in the configuration. Because we cannot check exploits against all Servlet containers and configuration variants, we strongly recommend upgrading your application.

Affected Spring Products and Versions

Spring Framework:

• 6.2.0 - 6.2.9
• 6.1.0 - 6.1.21
• 6.0.0 - 6.0.29
• 5.3.0 - 5.3.43
• Older, unsupported versions are also affected.

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.

No further mitigation steps are necessary.

Credit

This issue was responsibly reported by 1ue and b1u3r from Vidar-Team, and Joakim Erdfelt from Webtide.

References

• https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N&version=3.1

History

• 2025-08-14: Initial vulnerability report published.

Affected product:

Apache CXF , Apache Log4j , Apache Struts , Apache Tapestry , Apache Tomcat , Eclipse Jetty , Spring , acegi-security , activemq , camel , cocoon , crash , jersey , taglibs-standard-impl , tika

Affected packages:

jetty.project @ 9.4.58.v20250814 (+7490 more)

Description

Spring Framework MVC applications can be vulnerable to a “Path Traversal Vulnerability” when deployed on a non-compliant Servlet container.

An application can be vulnerable when all the following are true:

• the application is deployed as a WAR or with an embedded Servlet container
• the Servlet container does not reject suspicious sequences
• the application serves static resources with Spring resource handling

We have verified that applications deployed on Apache Tomcat or Eclipse Jetty are not vulnerable, as long as default security features are not disabled in the configuration. Because we cannot check exploits against all Servlet containers and configuration variants, we strongly recommend upgrading your application.

Affected Spring Products and Versions

Spring Framework:

• 6.2.0 - 6.2.9
• 6.1.0 - 6.1.21
• 6.0.0 - 6.0.29
• 5.3.0 - 5.3.43
• Older, unsupported versions are also affected.

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.

No further mitigation steps are necessary.

Credit

This issue was responsibly reported by 1ue and b1u3r from Vidar-Team, and Joakim Erdfelt from Webtide.

References

• https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N&version=3.1

History

• 2025-08-14: Initial vulnerability report published.