CVE-2017-1000479
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 31.7% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 31.7% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 31.7% · EPSS, next 30 days
- Weakness
- CWE-352 · Cross-site request forgery
- Record status
- Modified
Affected
- Netgate Pfsense ≤ 2.4.1
- Opnsense Project Opnsense < 16.1.16
Attack profile CVSS 3.0 · 8.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-1000479.md and follow it. Check whether this project is affected by CVE-2017-1000479. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- 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://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
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