What is the CVSS score of CVE-2015-5258?

CVE-2015-5258 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2015-5258?

Yes, a patch is available for CVE-2015-5258. Update the affected software to the latest version immediately.

Fedora CVE-2015-5258

HIGH

Cross-Site Request Forgery (CSRF) (CWE-352)

2017-08-22 secalert@redhat.com

CSRF Fedora Spring Social

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Aug 22, 2017 - 18:29 cve.org

HIGH 8.8

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

7 maven packages depend on org.springframework.social:spring-social-core (7 direct, 0 indirect)

Ecosystem-wide dependent count for version 1.1.3.RELEASE.

DescriptionCVE.org

Cross-site request forgery (CSRF) vulnerability in springframework-social before 1.1.3.

AnalysisAI

Cross-site request forgery (CSRF) vulnerability in springframework-social before 1.1.3. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity.

Technical ContextAI

This vulnerability is classified as Cross-Site Request Forgery (CSRF) (CWE-352), which allows attackers to trick authenticated users into performing unintended actions. Cross-site request forgery (CSRF) vulnerability in springframework-social before 1.1.3. Affected products include: Fedoraproject Fedora, Vmware Spring Social. Version information: before 1.1.3..

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Implement anti-CSRF tokens, validate Origin/Referer headers, use SameSite cookie attribute.