CVE-2019-11269: Open Redirect in Spring Security OAuth

CVE-2019-11269 · Severity: low · CVSS 3.1 · Published 2019-06-13

Open Redirect in Spring Security OAuth

Vendors: Maven.

Quick answers

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

Affected products

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

Identifiers

  • CVE-2019-11269
  • GHSA-mmf6-6597-3v6m

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