CVE-2015-1445
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 · uneditedHTTP header injection in the httpd package in fli4l before 3.10.1 and 4.0 before 2015-01-30.
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 · moderate confidenceHTTP header injection vulnerability in fli4l's httpd web server package allows attackers to inject arbitrary headers or perform HTTP response splitting attacks by including unsanitized user input in HTTP headers. This affects fli4l versions before 3.10.1 and 4.0 before 2015-01-30.
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<= 3.10.0= 4.0CVSS 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
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 fli4l is runningAccess the fli4l router's web administration interface via browser (typically http://fli4l or the router's IP address) or check for fli4l processes on the system using 'ps | grep fli4l' via console/SSH.Affected if The system is running fli4l and the httpd web server package is accessible.
-
Identify fli4l versionIn the web interface, navigate to the System > Information page to view the installed fli4l version. Alternatively, check the version.txt file in the /boot directory if console access is available.Affected if The displayed version is 3.10.0 or earlier, or version 4.0 with a build date before 2015-01-30.
-
Confirm httpd package is enabledCheck the fli4l configuration (typically in /etc/config.txt or via the web interface under Package Configuration) to verify that the httpd package is loaded and active.Affected if The httpd package is enabled and serving the web interface.
-
Assess HTTP header exposureReview any custom configurations or plugins that add custom HTTP headers (such as user-supplied values in redirects or cookie headers). Test by providing input containing carriage return and line feed characters (CRLF) in parameters that appear in HTTP responses.Affected if User-controlled input is reflected in HTTP response headers without sanitization of CRLF sequences.
The environment is affected if fli4l version is 3.10.0 or earlier, or version 4.0 built before 2015-01-30, and the httpd web server package is enabled with user input able to reach HTTP headers.
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 dataUpgrade to fli4l version 3.10.1 or later, or version 4.0 after 2015-01-30. If upgrading is not feasible, implement strict input validation to sanitize any user-controlled data before inserting it into HTTP response headers.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1445 — 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-2015-1445 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