p PatchFirst

PatchFirst · Latest vulnerabilities

libspring-java vulnerabilities · Page 4

Vulnerabilities published for libspring-java in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 81

  1. CVE-2013-6430

    Medium · CVSS 5.4EPSS 1.77%Fix available

    CVE-2013-6430

    The JavaScriptUtils.javaScriptEscape method in web/util/JavaScriptUtils.java in Spring MVC in Spring Framework before 3.2.2 does not properly escape certain characters, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a (1) line separator or (2) paragraph separator Unicode character or (3) left or (4) right angle bracket.

    • Update to 3.0.6.RELEASE-11
    Published Updated
  2. CVE-2016-1000027

    Critical · CVSS 9.8EPSS 33.18%Fix available

    CVE-2016-1000027

    Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required. NOTE: the vendor's position is that untrusted data is not an intended use case. The product's behavior will not be changed because some users rely on deserialization of trusted data.

    • Update to 4.2.7-1
    Published Updated
  3. CVE-2018-15756

    High · CVSS 7.5EPSS 8.8%Fix available

    DoS Attack via Range Requests

    Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources through the ResourceHttpRequestHandler, or starting in 5.0 when an annotated controller returns an org.springframework.core.io.Resource. A malicious user (or attacker) can add a range header with a high number of ranges, or with wide ranges that overlap, or both, for a denial of service attack. This vulnerability affects applications that depend on either spring-webmvc or spring-webflux. Such applications must also have a registration

    • Update to 4.3.21-1
    Published Updated
  4. CVE-2018-11040

    High · CVSS 7.5EPSS 3.18%Fix available

    CVE-2018-11040

    Spring Framework, versions 5.0.x prior to 5.0.7 and 4.3.x prior to 4.3.18 and older unsupported versions, allows web applications to enable cross-domain requests via JSONP (JSON with Padding) through AbstractJsonpResponseBodyAdvice for REST controllers and MappingJackson2JsonView for browser requests. Both are not enabled by default in Spring Framework nor Spring Boot, however, when MappingJackson2JsonView is configured in an application, JSONP support is automatically ready to use through the "jsonp" and "callback" JSONP parameters, enabling cross-domain requests.

    • Update to 4.3.19-1
    Published Updated
  5. CVE-2018-11039

    Medium · CVSS 5.9EPSS 2.77%Fix available

    CVE-2018-11039

    Spring Framework (versions 5.0.x prior to 5.0.7, versions 4.3.x prior to 4.3.18, and older unsupported versions) allow web applications to change the HTTP request method to any HTTP method (including TRACE) using the HiddenHttpMethodFilter in Spring MVC. If an application has a pre-existing XSS vulnerability, a malicious user (or attacker) can use this filter to escalate to an XST (Cross Site Tracing) attack.

    • Update to 4.3.19-1
    Published Updated
  6. CVE-2018-1257

    Medium · CVSS 6.5EPSS 3.02%Fix available

    CVE-2018-1257

    Spring Framework, versions 5.0.x prior to 5.0.6, versions 4.3.x prior to 4.3.17, and older unsupported versions allows applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a regular expression, denial of service attack.

    • Update to 4.3.19-1
    Published Updated
  7. CVE-2018-1272

    High · CVSS 7.5EPSS 3.06%Fix available

    CVE-2018-1272

    Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, provide client-side support for multipart requests. When Spring MVC or Spring WebFlux server application (server A) receives input from a remote client, and then uses that input to make a multipart request to another server (server B), it can be exposed to an attack, where an extra multipart is inserted in the content of the request from server A, causing server B to use the wrong value for a part it expects. This could to lead privilege escalation, for example, if the part content represents a username or user roles.

    • Update to 4.3.19-1
    Published Updated
  8. CVE-2018-1270

    Critical · CVSS 9.8EPSS 77.63%Fix available

    CVE-2018-1270

    Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack.

    • Update to 4.3.19-1
    Published Updated
  9. CVE-2018-1199

    Medium · CVSS 5.3EPSS 2.8%Fix available

    CVE-2018-1199

    Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the p

    • Update to 4.3.14-1
    Published Updated
  10. CVE-2016-5007

    High · CVSS 7.5EPSS 2.8%Fix available

    CVE-2016-5007

    Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Sprin

    • Update to 4.3.2-1
    Published Updated
  11. CVE-2015-5211

    Critical · CVSS 9.6EPSS 2.56%Fix available

    CVE-2015-5211

    Under some situations, the Spring Framework 4.2.0 to 4.2.1, 4.0.0 to 4.1.7, 3.2.0 to 3.2.14 and older unsupported versions is vulnerable to a Reflected File Download (RFD) attack. The attack involves a malicious user crafting a URL with a batch script extension that results in the response being downloaded rather than rendered and also includes some input reflected in the response.

    • Update to 4.1.9-1
    Published Updated
  12. CVE-2014-0225

    High · CVSS 8.8EPSS 1.47%Fix available

    CVE-2014-0225

    When processing user provided XML documents, the Spring Framework 4.0.0 to 4.0.4, 3.0.0 to 3.2.8, and possibly earlier unsupported versions did not disable by default the resolution of URI references in a DTD declaration. This enabled an XXE attack.

    • Update to 3.0.6.RELEASE-14
    Published Updated
  13. CVE-2014-0054

    Not ratedEPSS 91.35%Fix available

    CVE-2014-0054

    The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External Entity (XXE) issue. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-4152, CVE-2013-7315, and CVE-2013-6429.

    • Update to 3.0.6.RELEASE-13
    Published Updated
  14. CVE-2013-6429

    Not ratedEPSS 90.56%Fix available

    CVE-2013-6429

    The SourceHttpMessageConverter in Spring MVC in Spring Framework before 3.2.5 and 4.0.0.M1 through 4.0.0.RC1 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External Entity (XXE) issue, and a different vulnerability than CVE-2013-4152 and CVE-2013-7315.

    • Update to 3.0.6.RELEASE-11
    Published Updated
  15. CVE-2013-7315

    Not ratedEPSS 5.07%Fix available

    CVE-2013-7315

    The Spring MVC in Spring Framework before 3.2.4 and 4.0.0.M1 through 4.0.0.M2 does not disable external entity resolution for the StAX XMLInputFactory, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML with JAXB, aka an XML External Entity (XXE) issue, and a different vulnerability than CVE-2013-4152. NOTE: this issue was SPLIT from CVE-2013-4152 due to different affected versions.

    • Update to 3.0.6.RELEASE-10
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →