What is the CVSS score of CVE-2013-4562?

CVE-2013-4562 has a CVSS 2.0 base score of 6.8 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:P/I:P/A:P. EPSS exploitation probability: 0.5%.

Is there a public PoC exploit available for CVE-2013-4562?

Yes, a public proof-of-concept exploit is available for CVE-2013-4562. Prioritise patching immediately. EPSS: 0.5%.

Is there a patch available for CVE-2013-4562?

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

Omniauth Facebook CVE-2013-4562

MEDIUM

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

2014-05-13 secalert@redhat.com

CSRF Omniauth Facebook

6.8

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

6.8 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

May 13, 2014 - 15:55 cve.org

MEDIUM 6.8

DescriptionCVE.org

The omniauth-facebook gem 1.4.1 before 1.5.0 does not properly store the session parameter, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via the state parameter.

AnalysisAI

The omniauth-facebook gem 1.4.1 before 1.5.0 does not properly store the session parameter, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via the state parameter. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable. Public exploit code available.

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. The omniauth-facebook gem 1.4.1 before 1.5.0 does not properly store the session parameter, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via the state parameter. Affected products include: Madeofcode Omniauth-Facebook. Version information: before 1.5.0.

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.