pfSense versions 2.4.1 and lower are vulnerable to clickjacking attacks in the CSRF error page resulting in privileged execution of arbitrary code, because the error detection occurs before an X-Frame-Options header is set. This is fixed in 2.4.2-RELEASE. OPNsense, a 2015 fork of pfSense, was not vulnerable since version 16.1.16 released on June 06, 2016. The unprotected web form was removed from the code during an internal security audit under "possibly insecure" suspicions.
References
Link | Resource |
---|---|
http://www.openwall.com/lists/oss-security/2017/11/22/7 | Exploit Mailing List Third Party Advisory |
https://doc.pfsense.org/index.php/2.4.2_New_Features_and_Changes | Issue Tracking Vendor Advisory |
https://github.com/opnsense/core/commit/d218b225 | Patch Third Party Advisory |
https://github.com/pfsense/pfsense/commit/386d89b07 | Patch Third Party Advisory |
https://www.netgate.com/blog/pfsense-2-4-2-release-p1-and-2-3-5-release-p1-now-available.html | Third Party Advisory |
https://www.securify.nl/en/advisory/SFY20171101/clickjacking-vulnerability-in-csrf-error-page-pfsense.html | Exploit Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2018-01-03 18:29
Updated : 2024-02-28 16:04
NVD link : CVE-2017-1000479
Mitre link : CVE-2017-1000479
CVE.ORG link : CVE-2017-1000479
JSON object : View
Products Affected
opnsense_project
- opnsense
netgate
- pfsense
CWE
CWE-352
Cross-Site Request Forgery (CSRF)