PfsenseApplication · Netgate
CVE-2014-4696
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple open redirect vulnerabilities in the Suricata package before 1.0.6 for pfSense through 2.1.4 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via (1) the referer parameter to suricata_rules_flowbits.php or (2) the returl parameter to suricata_select_alias.php.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpen redirect vulnerabilities in the Suricata pfSense package allow attackers to craft malicious URLs using the referer parameter in suricata_rules_flowbits.php and the returl parameter in suricata_select_alias.php. User-supplied input is used in HTTP redirects without proper validation, enabling phishing attacks where victims believe they are visiting the legitimate pfSense interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
PfsenseApplication
<= 2.1.4= 2.1.3
Suricata PackageApplication
<= 1.0.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Suricata package is installedAccess pfSense web interface, navigate to Package Manager and check if Suricata appears in the installed packages list, or run 'pkg info | grep suricata' via Diagnostics > Command PromptAffected if Suricata package is listed as installed
-
Check Suricata package versionIn pfSense Package Manager, find the Suricata package entry and note the installed version number, or run 'pkg info suricata' via Diagnostics > Command PromptAffected if Version is 1.0.5 or lower (1.0.5, 1.0.4, 1.0.3, etc.)
-
Check pfSense base system versionIn pfSense web interface, go to System > General and view the version information, or run 'pfSense -v' via Diagnostics > Command PromptAffected if Version is 2.1.4 or 2.1.3
-
Locate vulnerable PHP filesAccess the pfSense file system via Diagnostics > File Editor or SSH, and search for suricata_rules_flowbits.php and suricata_select_alias.php in the Suricata package directory (typically /usr/local/www/suricata/)Affected if Both PHP files exist in the Suricata package directory, confirming the vulnerable code is present
You are affected if the Suricata package version is 1.0.5 or lower AND the pfSense version is 2.1.3 or 2.1.4, as both the vulnerable PHP files and the unpatched package versions must be present for this open redirect vulnerability to be exploitable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Suricata package to version 1.0.6 or later. If immediate update is not possible, implement input validation to ensure redirect targets are relative paths or trusted domains, avoiding use of user-supplied input directly in redirect locations.
Fix this in Pfsense
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4696 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-4696 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data