Skip to content
Noroxi
CVE-2019-3778· NVD / CVE Program· CNA dell

Open Redirect in spring-security-oauth2

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 16.5% (FIRST EPSS); higher than 96.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: org.springframework.security.oauth:spring-security-oauth (Maven) 2.1.4.RELEASE, 2.2.4.RELEASE, 2.3.5.RELEASE; org.springframework.security.oauth:spring-security-oauth2 (Maven) 2.1.4.RELEASE, 2.2.4.RELEASE, 2.3.5.RELEASE.

Low priority for now. Upgrade to org.springframework.security.oauth:spring-security-oauth (Maven) 2.1.4.RELEASE, 2.2.4.RELEASE, 2.3.5.RELEASE; org.springframework.security.oauth:spring-security-oauth2 (Maven) 2.1.4.RELEASE, 2.2.4.RELEASE, 2.3.5.RELEASE or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Spring Security OAuth, versions 2.3 prior to 2.3.5, and 2.2 prior to 2.2.4, and 2.1 prior to 2.1.4, and 2.0 prior to 2.0.17, and older unsupported versions could be susceptible to an open redirector attack that can leak an authorization code. A malicious user or attacker can craft a request to the authorization endpoint using the authorization code grant type, and specify a manipulated redirection URI via the "redirect_uri" parameter. This can cause the authorization server to redirect the resource owner user-agent to a URI under the control of the attacker with the leaked authorization code. This vulnerability exposes applications that meet all of the following requirements: Act in the role of an Authorization Server (e.g. @EnableAuthorizationServer) and uses the DefaultRedirectResolver in the AuthorizationEndpoint. This vulnerability does not expose applications that: Act in the role of an Authorization Server and uses a different RedirectResolver implementation other than DefaultRedirectResolver, act in the role of a Resource Server only (e.g. @EnableResourceServer), act in the role of a Client only (e.g. @EnableOAuthClient).

MediumCVSS 6.5 · v3.1—Proof of concept Fix available
Published
Mar 7, 2019
Updated
Jun 16, 2026
EPSS
16.6% · 97th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
5 / 30 · 16.6%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2019-3778

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for pivotal software records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
pivotal softwarespring security oauth
oraclebanking corporate lending

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • oracle banking corporate lending14.1.0
  • oracle banking corporate lending14.3.0
  • oracle banking corporate lending14.4.0
  • pivotal software spring security oauth2.0.0 and later · before 2.0.17
  • pivotal software spring security oauth2.3.0 and later · before 2.3.5
  • pivotal software spring security oauth2.1.0 and later · before 2.1.4
  • pivotal software spring security oauth2.2.0 and later · before 2.2.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.

  • Spring Spring Security OAuth

    • 2.3 and later · before 2.3.5.RELEASEaffected
    • 2.0 and later · before 2.0.17.RELEASEaffected
    • 2.1 and later · before 2.1.4.RELEASEaffected
    • 2.2 and later · before 2.2.4.RELEASEaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.springframework.security.oauth:spring-security-oauthfrom 2.1.0.RELEASE · before 2.1.4.RELEASE2.1.4.RELEASE
Mavenorg.springframework.security.oauth:spring-security-oauthfrom 2.2.0.RELEASE · before 2.2.4.RELEASE2.2.4.RELEASE
Mavenorg.springframework.security.oauth:spring-security-oauthfrom 2.3.0.RELEASE · before 2.3.5.RELEASE2.3.5.RELEASE
Mavenorg.springframework.security.oauth:spring-security-oauthbefore 2.0.17.RELEASE2.0.17.RELEASE
Mavenorg.springframework.security.oauth:spring-security-oauth2from 2.1.0.RELEASE · before 2.1.4.RELEASE2.1.4.RELEASE
Mavenorg.springframework.security.oauth:spring-security-oauth2from 2.2.0.RELEASE · before 2.2.4.RELEASE2.2.4.RELEASE
Mavenorg.springframework.security.oauth:spring-security-oauth2from 2.3.0.RELEASE · before 2.3.5.RELEASE2.3.5.RELEASE
Mavenorg.springframework.security.oauth:spring-security-oauth2before 2.0.17.RELEASE2.0.17.RELEASE

Same product

pivotal software: all records

Other highest-scoring records for the same primary product.

  • CVE-2018-1260Spring Security OAuth, versions 2.3 prior to 2.3.3, 2.2 prior to 2.2.2, 2.1 prior to 2.1.2, 2.0 prior to 2.0.15 and older unsupported versio
    42Plan
  • CVE-2018-15758Privilege Escalation in spring-security-oauth2
    33Monitor
  • CVE-2019-11269Open Redirector in spring-security-oauth2
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.springframework.security.oauth:spring-security-oauth2.0.17.RELEASEPackage registry (OSV)
Maven:org.springframework.security.oauth:spring-security-oauth2.1.4.RELEASEPackage registry (OSV)
Maven:org.springframework.security.oauth:spring-security-oauth2.2.4.RELEASEPackage registry (OSV)
Maven:org.springframework.security.oauth:spring-security-oauth2.3.5.RELEASEPackage registry (OSV)
Maven:org.springframework.security.oauth:spring-security-oauth22.0.17.RELEASEPackage registry (OSV)
Maven:org.springframework.security.oauth:spring-security-oauth22.1.4.RELEASEPackage registry (OSV)
Maven:org.springframework.security.oauth:spring-security-oauth22.2.4.RELEASEPackage registry (OSV)
Maven:org.springframework.security.oauth:spring-security-oauth22.3.5.RELEASEPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×1
  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrywebapps2019-06-17
Proof-of-concept repository on GitHubstars:02019-10-14

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+101 d
  3. TodayOct 14, 2026+2778 d
EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records