Patchfirst
CVE-2016-4977 Public exploit EPSS 80.0%

When processing authorization requests using the whitelabel views in Spring Security OAuth 2.0.0 to 2.0.9 and 1.0.0 to…

Fix:upgrade spring-security-oauth2 to 2.0.17.RELEASE or later also fixes CVE-2018-15758, CVE-2019-3778 Details ↓

Pivotal · Spring Security OAuth

Summary

The flaw is in the whitelabel views of Pivotal's Spring Security OAuth component, where the response_type parameter of authorization requests is evaluated as a Spring SpEL expression instead of being treated as plain data.

Official description · CVE.org

When processing authorization requests using the whitelabel views in Spring Security OAuth 2.0.0 to 2.0.9 and 1.0.0 to 1.0.5, the response_type parameter value was executed as Spring SpEL which enabled a malicious user to trigger remote code execution via the crafting of the value for response_type.

Breakdown
59.9 / 100
Exploited
Yes, in VulnCheck KEV
Reports
0
Tactics
0/15

First seen exploited 7 years after disclosure. Public exploit code (PoC-in-GitHub) appeared 5 years after disclosure.

  1. Disclosedday 0
  2. Public exploit codePoC-in-GitHub+5 yrs
  3. First seen exploitedVulnCheck KEV evidence+7 yrs

4 fixes in spring-security-oauth2 over 21 months. The latest fix listed for spring-security-oauth2 is 2.3.5.RELEASE.

Fixes in spring-security-oauth2Maven package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 2.0.10CVE-2016-497725 May 2017
  2. 2.3.3CVE-2018-126011 May 2018
  3. 2.3.4.RELEASECVE-2018-1575818 Oct 2018
  4. 2.3.5.RELEASECVE-2019-37787 Mar 2019Latest listed

Affected versions and fixes

as published in the CVE record

Pivotal Spring Security OAuth

Affected: 2.0.0 to 2.0.9 · 1.0.0 to 1.0.5

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: org.springframework.security.oauth:spring-security-oauth2.

Mavenorg.springframework.security.oauth:spring-security-oauth2GHSA-7q9c-h23x-65fq

Upgrade to 2.0.17.RELEASE or later

Fixes this CVE and 2 other known vulnerabilities in this package (CVE-2018-15758, CVE-2019-3778).

Set the version to 2.0.17.RELEASE or later in your pom.xml or build.gradle.

First fixed in 2.0.10 for CVE-2016-4977.

Affected versions, by release line

If you runUpgrade to
2.0.0 up to 2.0.102.0.17.RELEASEfirst fix for this CVE: 2.0.10
1.0.0 up to 1.0.5

Still affected on this line by CVE-2019-3778 (fixed in 2.0.17.RELEASE, a newer line).

1.0.5

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

References

6 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close