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

CVE-2015-0115 has a CVSS 2.0 base score of 6.0 (Medium). CVSS vector: AV:N/AC:M/Au:S/C:P/I:P/A:P. EPSS exploitation probability: 0.1%.

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

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

Leads CVE-2015-0115

MEDIUM

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

2015-06-28 psirt@us.ibm.com

IBM CSRF Leads

6.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

6.0 MEDIUM

AV:N/AC:M/Au:S/C:P/I:P/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:S/C:P/I:P/A:P

Attack Vector

Network

Attack Complexity

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Jun 28, 2015 - 22:59 cve.org

MEDIUM 6.0

DescriptionCVE.org

Cross-site request forgery (CSRF) vulnerability in IBM Leads 7.x, 8.1.0 before 8.1.0.14, 8.2, 8.5.0 before 8.5.0.7.3, 8.6.0 before 8.6.0.8.1, 9.0.0 through 9.0.0.4, 9.1.0 before 9.1.0.6.1, and 9.1.1 before 9.1.1.0.2 allows remote authenticated users to hijack the authentication of customer accounts.

AnalysisAI

Cross-site request forgery (CSRF) vulnerability in IBM Leads 7.x, 8.1.0 before 8.1.0.14, 8.2, 8.5.0 before 8.5.0.7.3, 8.6.0 before 8.6.0.8.1, 9.0.0 through 9.0.0.4, 9.1.0 before 9.1.0.6.1, and 9.1.1. Rated medium severity (CVSS 6.0), this vulnerability is remotely exploitable.

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 IBM Leads 7.x, 8.1.0 before 8.1.0.14, 8.2, 8.5.0 before 8.5.0.7.3, 8.6.0 before 8.6.0.8.1, 9.0.0 through 9.0.0.4, 9.1.0 before 9.1.0.6.1, and 9.1.1 before 9.1.1.0.2 allows remote authenticated users to hijack the authentication of customer accounts. Affected products include: Ibm Leads. Version information: before 8.1.0.14.

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.