What’s Vulnerable › Vulnerabilities

CVE-2017-1000479

• Severity: high (CVSS 8.8 v3.0)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 31.7% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2018-01-03 · updated 2026-06-17
• Weakness: CWE-352

Description

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.

Affected products

• Netgate pfSense: through 2.4.1
• Opnsense Project Opnsense: before 16.1.16 — fixed in 16.1.16

How to fix

Upgrade to a fixed version: Opnsense Project Opnsense 16.1.16. Check the vendor advisory for mitigations.

References

• http://www.openwall.com/lists/oss-security/2017/11/22/7
• https://doc.pfsense.org/index.php/2.4.2_New_Features_and_Changes
• https://github.com/opnsense/core/commit/d218b225
• https://github.com/pfsense/pfsense/commit/386d89b07
• https://www.netgate.com/blog/pfsense-2-4-2-release-p1-and-2-3-5-release-p1-now-available.html
• https://www.securify.nl/en/advisory/SFY20171101/clickjacking-vulnerability-in-csrf-error-page-pfsense.html
• http://www.openwall.com/lists/oss-security/2017/11/22/7
• https://doc.pfsense.org/index.php/2.4.2_New_Features_and_Changes
• https://github.com/opnsense/core/commit/d218b225
• https://github.com/pfsense/pfsense/commit/386d89b07
• https://www.netgate.com/blog/pfsense-2-4-2-release-p1-and-2-3-5-release-p1-now-available.html
• https://www.securify.nl/en/advisory/SFY20171101/clickjacking-vulnerability-in-csrf-error-page-pfsense.html

Get alerted when CVE-2017-1000479 or the next vulnerability affects your stack