PatchTheCVEjanrain vulnerabilities
Recent CVEs affecting janrain products. 4 tracked.
janrain has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2016-02-01. Highest priority: CVE-2013-4701 (score 53/100).
- CVE-2016-2049 HIGH 8.8 MITIGATE examples/consumer/common.php in JanRain PHP OpenID library (aka php-openid) improperly checks the openid.realm
- CVE-2013-4701 HIGH 7.5 UPGRADE Auth/Yadis/XML.php in PHP OpenID Library 2.2.2 and earlier allows remote attackers to read arbitrary files, se
- CVE-2013-1812 MEDIUM 4.3 MITIGATE UPGRADE The ruby-openid gem before 2.2.2 for Ruby allows remote OpenID providers to cause a denial of service (CPU con
- CVE-2012-2296 MEDIUM 5.0 DOWNGRADE The Janrain Engage (formerly RPX) module for Drupal 6.x-1.x
FAQ
How do I fix janrain vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is janrain being exploited right now?
None of the tracked janrain CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which janrain CVE should I patch first?
CVE-2013-4701 currently ranks highest (53/100): Auth/Yadis/XML.php in PHP OpenID Library 2.2.2 and earlier allows remote attackers to read arbitrary files, se.