# CVE-2017-1000479: Cross-site request forgery in n/a

> Clickjacking in pfSense CSRF error page allows privileged arbitrary code execution due to missing X-Frame-Options header.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** CVE-2018-5191, GHSA-vh6j-wmcp-r6j7

## What is CVE-2017-1000479?

CVE-2017-1000479 is a high-severity vulnerability in n/a, published on 3 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2017-1000479?

It affects 2 products.


Products: Netgate Pfsense, Opnsense Project Opnsense.

## How do I fix CVE-2017-1000479?

No fix has been published for CVE-2017-1000479 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-1000479 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-1000479 exists.

Public exploit code:

- Clickjacking Vulnerability In CSRF Error Page pfSense (metasploit)

## Other vulnerabilities in n/a

- [CVE-2019-16915](https://insights.sbomify.com/CVE-2019-16915/): Path traversal in n/a (critical 9.8)
- [CVE-2020-21487](https://insights.sbomify.com/CVE-2020-21487/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2024-46538](https://insights.sbomify.com/CVE-2024-46538/): Cross-site scripting in n/a (critical 9.3)
- [CVE-2023-48123](https://insights.sbomify.com/CVE-2023-48123/): Command injection in n/a (high 8.8)
- [CVE-2023-42326](https://insights.sbomify.com/CVE-2023-42326/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000479 and fix it if it is affected.

What it is: CVE-2017-1000479 is a high-severity vulnerability in n/a, published on 3 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-1000479 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-1000479/ (Markdown: https://insights.sbomify.com/CVE-2017-1000479/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-1000479
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-1000479
- OSV: https://osv.dev/vulnerability/CVE-2017-1000479

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-1000479/
Summaries are generated and may contain mistakes; the official description above is the record.