CVE-2014-1904: Cross-Site Scripting (XSS) Vulnerability in org.springframework:spring-webmvc

Summary

14/05/2022
Yes i
Moderate
Not published

CVE-2014-1904: Improper Neutralization of Input During Web Page Generation in Spring Framework. Affects org.springframework:spring-webmvc across 2 version ranges.

>= 3.0.0, < 3.2.8.RELEASE >= 4.0.0, < 4.0.2.RELEASE

Fixed in 3.2.8.RELEASE or 4.0.2.RELEASE, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2014-1904 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The org.springframework:spring-webmvc package is a part of the Spring Framework, which is a popular Java-based framework for building web applications. Spring MVC, a module within the Spring Framework, provides support for building web applications using the Model-View-Controller (MVC) architectural pattern. The package includes various classes and components that facilitate the development of web applications, including the FormTag class in the web/servlet/tags/form directory. This vulnerability affects versions 3.0.0 to 3.2.7.RELEASE and 4.0.0 to 4.0.1.RELEASE of the package.

Vulnerability Detail

The vulnerability identified as CVE-2014-1904 is an instance of improper neutralization of input during web page generation in the Spring Framework. Specifically, it is a cross-site scripting (XSS) vulnerability in the FormTag.java file within the Spring MVC module. This vulnerability allows remote attackers to inject arbitrary web script or HTML via the requested URI in a default action. The impact of this vulnerability can range from unauthorized access to sensitive information to the execution of malicious code on the affected web application.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 3.0.0, < 3.2.8.RELEASE 3.2.8.RELEASE
  • >= 4.0.0, < 4.0.2.RELEASE 4.0.2.RELEASE

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, developers can manually sanitize user input before using it in the requested URI. This can be done by applying appropriate input validation and output encoding techniques. However, it is strongly advised to apply the recommended fix by upgrading to the fixed versions of the package as soon as possible.

Conclusion

In conclusion, the org.springframework:spring-webmvc package is vulnerable to a cross-site scripting (XSS) vulnerability in the FormTag.java file. This vulnerability allows remote attackers to inject arbitrary web script or HTML, potentially leading to unauthorized access to sensitive information or the execution of malicious code. To mitigate this vulnerability, it is recommended to upgrade to the fixed versions of the package. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.springframework:spring-webmvc →

Share this vulnerability

FAQ

The vulnerability allows remote attackers to inject arbitrary web script or HTML, potentially leading to unauthorized access to sensitive information or the execution of malicious code on the affected web application.

Versions 3.0.0 to 3.2.7.RELEASE and 4.0.0 to 4.0.1.RELEASE of the package are affected by this vulnerability.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it in real-time and alert you if any open-source vulnerabilities, including this one, are detected.

A temporary workaround is to manually sanitize user input before using it in the requested URI. However, it is strongly recommended to apply the fix by upgrading to the fixed versions of the package.

You can find more information about this vulnerability, including its impact and the fixed versions of the package, in the advisory on the GitHub Advisory Database: [link to advisory]

Related vulnerabilities

Recent vulnerabilities recorded for org.springframework:spring-webmvc.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 3.0.0, < 3.2.8.RELEASE 3.2.8.RELEASE
  • >= 4.0.0, < 4.0.2.RELEASE 4.0.2.RELEASE

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback