Deserialization of Untrusted Data The advisory has been revoked - it doesn't affect any version of package org.springframework:spring-web (opens in a new tab)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGSPRINGFRAMEWORK-570456
- published2 Dec 2024
- disclosed2 Jan 2020
- creditUnknown
Introduced: 2 Jan 2020
CVE-2016-1000027 (opens in a new tab)How to fix?
Upgrade org.springframework:spring-web to version 6.0.0 or higher.
Amendment
This was deemed not a vulnerability.
Overview
org.springframework:spring-web is a package that provides a comprehensive programming and configuration model for modern Java-based enterprise applications - on any kind of deployment platform.
Affected versions of this package are vulnerable to Deserialization of Untrusted Data. This vulnerability describes unsafe usage of Spring-web. So if a user utilizes spring-web in a particular way, it leads to code execution, and the remediation here from the developer is simply putting a note stating that. (See: https://github.com/spring-projects/spring-framework/commit/76964e16efbcee7c19608e826aa26c032493baa0) . Snyk does not mark unsafe usage of dependencies as vulnerabilities since it is not a direct dependency vulnerability, its more about how the dependency is being used by a user, and furthermore, there is no fix from the spring maintainer here.