Bug 853641 (CVE-2013-4562) - VUL-0: CVE-2013-4562: rubygem-omniauth-facebook: CSRF vulnerability
Summary: VUL-0: CVE-2013-4562: rubygem-omniauth-facebook: CSRF vulnerability
Status: RESOLVED FIXED
Alias: CVE-2013-4562
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Jordi Massaguer
QA Contact: Security Team bot
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-04 13:40 UTC by Alexander Bergmann
Modified: 2013-12-18 13:59 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Bergmann 2013-12-04 13:40:14 UTC
Public via ruby-security-ann.

# RubyGem omniauth-facebook CSRF vulnerability

There is a security vulnerability in the CSRF protection of omniauth-facebook 1.4.1. This vulnerability has been assigned the CVE identifier CVE-2013-4562.

    Versions affected: 1.4.1
    Not affected:      <= 1.4.0 (*)
    Fixed versions:    >= 1.5.0
   
(*) Versions <= 1.4.0 did not have any CSRF protection. So, while this vulnerability does not directly affect versions <= 1.4.0, downgrading to <= 1.4.0 is not a fix.

## Impact

Because of the way that omniauth-facebook supports setting a per-request state parameter by storing it in the session, it is possible to circumvent the automatic CSRF protection. Therefore the CSRF added in 1.4.1 should be considered broken.

If you are currently providing a custom state, you will need to store and retrieve this yourself (for example, by using the session store) to use 1.5.0.

All users running an affected release should upgrade to 1.5.0.

## Releases

The 1.5.0 releases is available at the normal locations.

## Workarounds

None.

## Credits

Egor Homakov (@homakov)

http://www.osvdb.org/show/osvdb/99693
Comment 1 Swamp Workflow Management 2013-12-04 23:00:49 UTC
bugbot adjusting priority
Comment 4 Alexander Bergmann 2013-12-18 13:31:34 UTC
Jordi, is this fixed from your side? When yes, this can be closed.
Comment 5 Jordi Massaguer 2013-12-18 13:59:13 UTC
Yes it is.