dbcve.org
Spring Security OauthFramework / library · Pivotal Software

CVE-2018-1260

CRITICAL · 9.8 CVSS v3.0 Published 2018-05-11
Fix available
A fix is available. Upgrade to after 2.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Spring 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 versions contains a remote code execution vulnerability. A malicious user or attacker can craft an authorization request to the authorization endpoint that can lead to remote code execution when the resource owner is forwarded to the approval endpoint.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spring Security OAuth contains a remote code execution vulnerability where a maliciously crafted authorization request to the authorization endpoint can lead to RCE when the resource owner is forwarded to the approval endpoint. This is a code injection flaw in the OAuth authorization flow.

MitigationUpgrade Spring Security OAuth to version 2.3.3, 2.2.2, 2.1.2, 2.0.15 or later to remediate the RCE vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring Security OauthFramework / library
Affected:<= 2.0.14>= 2.1, <= 2.1.1>= 2.2, <= 2.2.1>= 2.3, <= 2.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Find the Spring Security OAuth version in your build configuration
    Inspect your Maven pom.xml or Gradle build.gradle file for the spring-security-oauth2-autoconfigure or spring-security-oauth2 dependency and note its version.
    Affected if The version falls within any of these ranges: <= 2.0.14, >= 2.1.0 <= 2.1.1, >= 2.2.0 <= 2.2.1, or >= 2.3.0 <= 2.3.2.
  2. Confirm OAuth2 authorization endpoint is enabled
    Check your Spring configuration (Java config or XML) for @EnableAuthorizationServer or AuthorizationServerConfigurerAdapter. Verify the authorization endpoint path is exposed, typically at /oauth/authorize.
    Affected if The authorization endpoint is exposed and accessible without additional restrictions.
  3. Verify user approval is enabled in the authorization server
    Inspect your AuthorizationServerConfigurerAdapter configuration. Look for the ApprovalStoreSettings or check if explicit approval (user_consent) is configured for the authorization endpoint.
    Affected if User approval/consent is enabled, allowing the resource owner to be forwarded to an approval endpoint during the OAuth flow.
  4. Check for runtime dependency on spring-security-oauth2
    At runtime, inspect the classpath for the presence of org.springframework.security.oauth2 package. Use your application's dependency management tool or examine the deployed WEB-INF/lib directory for oauth2 jars.
    Affected if The spring-security-oauth2 or spring-security-oauth2-autoconfigure jar is present in the runtime classpath.

You are affected if your application runs Spring Security OAuth within any of the vulnerable version ranges AND has the OAuth authorization endpoint with user approval enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.3.2
Interim mitigation

Upgrade Spring Security OAuth to version 2.3.3, 2.2.2, 2.1.2, 2.0.15 or later to remediate the RCE vulnerability.

Recommended fix High confidence

Spring Security OAuth 2.3.3 (or 2.0.15/2.1.2/2.2.2 depending on your major version branch)

  1. 1. Identify all dependencies in your project that use Spring Security OAuth (check pom.xml, build.gradle, or equivalent)
  2. 2. Locate the current version of org.springframework.security.oauth:spring-security-oauth2 in your dependency management
  3. 3. Update the version to 2.3.3 (or the appropriate version for your major line: 2.0.15 for 2.0.x, 2.1.2 for 2.1.x, 2.2.2 for 2.2.x, 2.3.3 for 2.3.x)
  4. 4. Run your build tool to resolve the new dependency (mvn clean install or gradle build)
  5. 5. Rebuild and redeploy your application
  6. 6. Test OAuth authorization flows including the authorization endpoint and approval redirect to verify the fix works
  7. 7. Verify no regression in existing OAuth functionality
Caveat Minor patch release; backward compatible but review release notes for any security-related configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Security Oauth Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1260 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data