CVE-2013-4593 json
omniauth-facebook Improper Authentication vulnerability
published 6y ago modified 4mo ago also GHSA-33vg-hpx5-pfxg , EUVD-2022-2099
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
RubyGem omniauth-facebook has an access token security vulnerability
Patch / fix
- rubygems omniauth-facebook 1.5.1
Is CVE-2013-4593 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.75% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | omniauth-facebook | <1.5.1 |
1.5.1 |
Affected products
- omniauth-facebook omniauth-facebook
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
openwall.com
/lists/oss-security/2013/11/18/6
web, mailing-list, patch, third-party-advisory
-
github.com
/simi/omniauth-facebook/commit/115c0a768cd6f4b9bfae8900f8e3fc4fbeec3ad8
web
-
security-tracker.debian.org
/tracker/CVE-2013-4593
web, third-party-advisory
-
access.redhat.com
/security/cve/cve-2013-4593
broken-link
-
exchange.xforce.ibmcloud.com
/vulnerabilities/89040
web, third-party-advisory, vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2013-4593
advisory
-
github.com
/simi/omniauth-facebook
package
Sources
- CVE List CVE-2013-4593
- GitHub Advisory GHSA-33vg-hpx5-pfxg
- NVD CVE-2013-4593
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.