CVE-2017-1000479

UnknownEPSS 32.77%

Last modified

CVE-2017-1000479 is a vulnerability of currently unknown severity. 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. EPSS estimates a 32.77% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
32.77%

98.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
NetgatePfsense<= 2.4.1
Opnsense ProjectOpnsense< 16.1.16

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-1000479?
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.
How severe is CVE-2017-1000479?
Severity scoring for CVE-2017-1000479 is pending analysis. The EPSS model estimates a 32.77% probability of exploitation in the next 30 days.
How do I fix CVE-2017-1000479?
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.

Are you affected by CVE-2017-1000479?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST