CVE-2017-1000479

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekWeaponized
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 33%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
70(Track)
EG Risk 70/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
98.2%
KEV
Not listed

Published

January 3, 2018

Last Modified

November 21, 2024

References (12)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:13 UTCEPSS rescore
  2. 2026-07-23 01:25 UTCEG score recompute
  3. 2026-07-22 22:04 UTCEG score recompute
  4. 2026-07-22 14:04 UTCEPSS rescore
  5. 2026-07-21 19:48 UTCOSV refresh
  6. 2026-07-21 15:21 UTCEPSS rescore
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-20 17:04 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-19 02:26 UTCEPSS rescore
  11. 2026-07-16 16:59 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 01:56 UTCEPSS rescore
  16. 2026-07-13 22:26 UTCEPSS rescore
  17. 2026-07-13 06:09 UTCEPSS rescore
  18. 2026-07-12 05:43 UTCEPSS rescore
  19. 2026-07-12 05:43 UTCEPSS rescore
  20. 2026-07-11 08:24 UTCEPSS rescore
  21. 2026-07-09 19:06 UTCEPSS rescore
  22. 2026-07-08 15:10 UTCEPSS rescore
  23. 2026-07-06 16:24 UTCEPSS rescore
  24. 2026-07-06 16:24 UTCEPSS rescore
  25. 2026-07-04 15:56 UTCOSV refresh
Show 51 more
  1. 2026-07-04 06:28 UTCEPSS rescore
  2. 2026-07-01 15:02 UTCEPSS rescore
  3. 2026-06-30 23:19 UTCEPSS rescore
  4. 2026-06-30 23:19 UTCEPSS rescore
  5. 2026-06-28 04:53 UTCEPSS rescore
  6. 2026-06-27 03:05 UTCEPSS rescore
  7. 2026-06-25 13:47 UTCEPSS rescore
  8. 2026-06-24 14:02 UTCEPSS rescore
  9. 2026-06-23 21:30 UTCEPSS rescore
  10. 2026-06-21 14:54 UTCEPSS rescore
  11. 2026-06-21 14:54 UTCEPSS rescore
  12. 2026-06-21 01:57 UTCEPSS rescore
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-18 17:50 UTCEPSS rescore
  15. 2026-06-18 17:50 UTCEPSS rescore
  16. 2026-06-17 17:50 UTCEPSS rescore
  17. 2026-06-17 17:50 UTCEPSS rescore
  18. 2026-06-16 17:50 UTCEPSS rescore
  19. 2026-06-16 03:13 UTCOSV refresh
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-14 23:14 UTCEPSS rescore
  22. 2026-06-14 23:14 UTCEPSS rescore
  23. 2026-06-13 22:57 UTCEPSS rescore
  24. 2026-06-13 22:57 UTCEPSS rescore
  25. 2026-06-12 23:09 UTCEPSS rescore
  26. 2026-06-11 13:57 UTCEPSS rescore
  27. 2026-06-08 14:14 UTCEPSS rescore
  28. 2026-06-07 15:22 UTCEPSS rescore
  29. 2026-06-07 15:22 UTCEPSS rescore
  30. 2026-06-06 13:45 UTCEPSS rescore
  31. 2026-06-06 13:45 UTCEPSS rescore
  32. 2026-06-05 22:44 UTCEPSS rescore
  33. 2026-06-04 13:10 UTCEPSS rescore
  34. 2026-06-04 13:10 UTCEPSS rescore
  35. 2026-06-02 20:10 UTCEPSS rescore
  36. 2026-06-01 13:49 UTCEPSS rescore
  37. 2026-06-01 13:49 UTCEPSS rescore
  38. 2026-05-31 22:28 UTCEPSS rescore
  39. 2026-05-31 22:28 UTCEPSS rescore
  40. 2026-05-31 00:14 UTCEPSS rescore
  41. 2026-05-29 13:41 UTCEPSS rescore
  42. 2026-05-28 13:42 UTCEPSS rescore
  43. 2026-05-28 13:42 UTCEPSS rescore
  44. 2026-05-28 12:56 UTCEG score recompute
  45. 2026-05-28 12:56 UTCGHSA enrichment
  46. 2026-05-27 13:38 UTCEPSS rescore
  47. 2026-05-27 13:38 UTCEPSS rescore
  48. 2026-05-26 13:42 UTCEPSS rescore
  49. 2026-05-26 13:42 UTCEPSS rescore
  50. 2026-05-26 07:17 UTCEPSS rescore
  51. 2026-05-25 12:46 UTCOSV refresh

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/unix/http/pfsense_clickjacking✓ verified
    First seen Nov 21, 2017

    Clickjacking Vulnerability In CSRF Error Page pfSense

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-1000479?
CVE-2017-1000479 is a high vulnerability published on January 3, 2018. 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…
When was CVE-2017-1000479 disclosed?
CVE-2017-1000479 was first published in the National Vulnerability Database on January 3, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-1000479 actively exploited?
CVE-2017-1000479 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-1000479?
CVE-2017-1000479 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2017-1000479?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-1000479, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-1000479

Explore →

Is Your Infrastructure Affected by CVE-2017-1000479?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs