CVE-2016-4977: Spring Security OAuth vulnerable to remote code execution (RCE) via specially crafted request using whitelabel views

CVE-2016-4977 · Severity: low · CVSS 3 · Published 2018-10-18

Spring Security OAuth vulnerable to remote code execution (RCE) via specially crafted request using whitelabel views

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

Quick answers

Is CVE-2016-4977 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-4977 being exploited in the wild.
How severe is CVE-2016-4977?
Low severity, with a CVSS score of 3, published 18 October 2018.
Which products and versions are affected?
org.springframework.security.oauth:spring-security-oauth2 (Maven) ECOSYSTEM:introduced=2.0.0,fixed=2.0.10.
Is there a fix for CVE-2016-4977?
Yes. org.springframework.security.oauth:spring-security-oauth2 (Maven): upgrade to 2.0.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2016-4977?
Check whether you run org.springframework.security.oauth:spring-security-oauth2 (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.oauth:spring-security-oauth2 (Maven): upgrade to 2.0.10 or later
    # set org.springframework.security.oauth:spring-security-oauth2 to 2.0.10 in your pom.xml or build.gradle

Affected products

  • org.springframework.security.oauth:spring-security-oauth2 (Maven) ECOSYSTEM:introduced=2.0.0,fixed=2.0.10

Identifiers

  • CVE-2016-4977
  • GHSA-7q9c-h23x-65fq

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