dbcve.org
FedoraOperating system · Fedoraproject

CVE-2015-5258

HIGH · 8.8 CVSS v3.1 Published 2017-08-22
Fix available
A fix is available. Upgrade to 1.1.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-site request forgery (CSRF) vulnerability in springframework-social before 1.1.3.

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 · moderate confidence

Cross-site request forgery (CSRF) vulnerability in Spring Social framework versions prior to 1.1.3. Attackers can exploit this to trick authenticated users into unknowingly performing unintended actions via malicious requests to the application.

MitigationUpgrade springframework-social to version 1.1.3 or later to obtain the security patch. Additionally, ensure proper CSRF token validation is enabled in the Spring Security configuration.

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
FedoraOperating system
Affected:= 23
Spring SocialFramework / library
Affected:< 1.1.3

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify Spring Social dependency in your project
    Search for spring-social-core or spring-social in your project's dependency manifest files (pom.xml, build.gradle, package.json, or similar). Also search for 'spring-social' strings in all JAR files within your application lib directory.
    Affected if Spring Social library is present in the application
  2. Determine installed Spring Social version
    Examine the version number of the spring-social-core or spring-social JAR file. In Maven projects, run 'mvn dependency:tree | grep spring-social' or check pom.xml for the version tag. In Gradle, check build.gradle for the spring-social version.
    Affected if The version number is less than 1.1.3 (e.g., 1.1.2, 1.1.1, 1.1.0, 1.0.x)
  3. Verify Spring Security CSRF protection configuration
    Inspect your Spring Security configuration XML file (typically security-config.xml or similar) or Java-based SecurityConfig class. Look for <csrf> element in the <http> configuration block, or look for .csrf() in Java config.
    Affected if CSRF protection is explicitly disabled or missing from the security configuration

Your application is affected if it uses Spring Social version prior to 1.1.3 AND CSRF protection is not properly enabled in your Spring Security configuration.

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.

From vendor data
Upgrade available Upgrade to 1.1.3 or later
Fixed in 1.1.3
Interim mitigation

Upgrade springframework-social to version 1.1.3 or later to obtain the security patch. Additionally, ensure proper CSRF token validation is enabled in the Spring Security configuration.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5258 — 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-2015-5258 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