CVE-2017-18076
HIGHCVSS 7.5/10EPSS 2.14%
Last modified
CVE-2017-18076 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. In strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is improperly protected because POST (in addition to GET) parameters are stored in the session and become available in the environment of the callback phase.. EPSS estimates a 2.14% chance of exploitation in the next 30 days.
Description
In strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is improperly protected because POST (in addition to GET) parameters are stored in the session and become available in the environment of the callback phase.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Omniauth | Omniauth | < 1.3.2 |
| Debian | Debian Linux | 8.0 |
| Debian | Debian Linux | 9.0 |
References
- https://bugs.debian.org/888523Issue Tracking, Third Party Advisory
- https://github.com/omniauth/omniauth/pull/867Patch, Third Party Advisory
- https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9bPatch, Third Party Advisory
- https://www.debian.org/security/2018/dsa-4109Third Party Advisory
- https://bugs.debian.org/888523Issue Tracking, Third Party Advisory
- https://github.com/omniauth/omniauth/pull/867Patch, Third Party Advisory
- https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9bPatch, Third Party Advisory
- https://www.debian.org/security/2018/dsa-4109Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-18076?
In strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is improperly protected because POST (in addition to GET) parameters are stored in the session and become available in the environment of the callback phase.
How severe is CVE-2017-18076?
CVE-2017-18076 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 2.14% probability of exploitation in the next 30 days.
How do I fix CVE-2017-18076?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-18070In wma_ndp_end_response_event_handler(), the variable len_en…
- CVE-2017-18071In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18072In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18073In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18074In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18075crypto/pcrypt.c in the Linux kernel before 4.14.13 mishandle…7.8
- CVE-2017-18077index.js in brace-expansion before 1.1.7 is vulnerable to Re…
- CVE-2017-18078systemd-tmpfiles in systemd before 237 attempts to support o…7.8
- CVE-2017-18079drivers/input/serio/i8042.c in the Linux kernel before 4.12.…7.8
- CVE-2017-18080The saveConfigureSecurity resource in Atlassian Bamboo befor…
- CVE-2017-18081The signupUser resource in Atlassian Bamboo before version 6…
- CVE-2017-18082The plan configure branches resource in Atlassian Bamboo bef…
Are you affected by CVE-2017-18076?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST