CVE-2017-1000247
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 · uneditedBritish Columbia Institute of Technology CodeIgniter 3.1.3 is vulnerable to HTTP Header Injection in the set_status_header() common function under Apache resulting in HTTP Header Injection flaws.
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 confidenceCodeIgniter 3.1.3 contains an HTTP Header Injection vulnerability in the set_status_header() common function. The function fails to properly validate or sanitize input when setting HTTP status headers, potentially allowing an attacker to inject arbitrary HTTP headers via CRLF injection when running under Apache.
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.1.3CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Identify the CodeIgniter versionLocate the version file or constant in your CodeIgniter installation (typically in the system directory or a VERSION file) and note the version numberAffected if The version is exactly 3.1.3
-
Locate the set_status_header() functionFind the set_status_header() function definition in your CodeIgniter core files (commonly in the common.php or equivalent core file)Affected if The function exists in your codebase (it is a core function in CodeIgniter 3.1.3)
-
Search for usages of set_status_header() with dynamic inputSearch your application code for calls to set_status_header() and examine whether any parameters come from user input, query strings, headers, or other untrusted sourcesAffected if set_status_header() is being called with unsanitized user-controlled data as the status code parameter
-
Check if running under ApacheExamine your server environment configuration to confirm the web server is Apache (as opposed to Nginx, IIS, or others)Affected if The application is running on Apache web server
-
Verify the function lacks input validationReview the set_status_header() function code to see if it validates the status code parameter for CRLF characters (\r\n) or other injection attemptsAffected if The function does not sanitize or validate the input for CRLF injection before setting the header
You are affected if you are running CodeIgniter 3.1.3 on Apache and your application uses set_status_header() with unsanitized user input, combined with a vulnerable version of the function that lacks CRLF injection protection.
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 a patched version of CodeIgniter that properly validates status codes and sanitizes input to prevent HTTP Header Injection. If immediate patching is not possible, review all calls to set_status_header() and ensure user-supplied data is not passed unsanitized.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000247 — 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-2017-1000247 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