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.
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
| Link | Tags |
|---|---|
| https://doc.pfsense.org/index.php/2.4.2_New_Features_and_Changes | issue tracking vendor 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://github.com/opnsense/core/commit/d218b225 | third party advisory patch |
| https://www.securify.nl/en/advisory/SFY20171101/clickjacking-vulnerability-in-csrf-error-page-pfsense.html | third party advisory exploit |
| https://github.com/pfsense/pfsense/commit/386d89b07 | third party advisory patch |
| http://www.openwall.com/lists/oss-security/2017/11/22/7 | mailing list exploit third party advisory |