CVE-2016-9879: Security Constraint Bypass in Spring Security

CVE-2016-9879 · Severity: low · CVSS 3 · Published 2020-09-15

Security Constraint Bypass in Spring Security

Technologies: org.springframework.security:spring-security-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2016-9879 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-9879 being exploited in the wild.
How severe is CVE-2016-9879?
Low severity, with a CVSS score of 3, published 15 September 2020.
Which products and versions are affected?
org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=0,fixed=3.2.10.RELEASE.
Is there a fix for CVE-2016-9879?
Yes. org.springframework.security:spring-security-core (Maven): upgrade to 3.2.10.RELEASE or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2016-9879?
Check whether you run org.springframework.security:spring-security-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.springframework.security:spring-security-core (Maven): upgrade to 3.2.10.RELEASE or later
    # set org.springframework.security:spring-security-core to 3.2.10.RELEASE in your pom.xml or build.gradle

Affected products

  • org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=0,fixed=3.2.10.RELEASE

Identifiers

  • CVE-2016-9879
  • GHSA-v35c-49j6-q8hq

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.