CVE-2013-4562 json
omniauth-facebook Cross-Site Request Forgery vulnerability
published 12y ago modified 4mo ago also GHSA-cf36-985g-v73c , EUVD-2017-0216
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2013-4562 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/mkdynamic/omniauth-facebook/commit/ccfcc26fe7e34acbd75ad4a095fd01ce5ff48ee7 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | omniauth-facebook | >=1.4.1, <1.5.0 |
1.5.0 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/mkdynamic/omniauth-facebook/commit/ccfcc26fe7e34acbd75ad4a095fd01ce5ff48ee7
web, exploit, patch
-
seclists.org
/oss-sec/2013/q4/264
mailing-list, web
-
osvdb.org
/99693
vdb-entry
-
groups.google.com
/d/msg/ruby-security-ann/-tJHNlTiPh4/9SJxdEWLIawJ
mailing-list, web
- osvdb.org /ref/99/omniauth-facebook_gem.txt
-
seclists.org
/oss-sec/2013/q4/267
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2013-4562
advisory
-
github.com
/mkdynamic/omniauth-faceboo
package
Sources
- CVE List CVE-2013-4562
- GitHub Advisory GHSA-cf36-985g-v73c
- NVD CVE-2013-4562
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.