Security readout for executives and security teams
Plain-English summary
CodeIgniter 3.1.3 has a reported HTTP header injection flaw in its set_status_header() function when used under Apache. In business terms, affected web applications may be able to produce unsafe HTTP responses. The public bundle does not provide a CVSS score, confirmed exploitation, or detailed fix text.
Executive priority
Treat this as a targeted legacy-framework risk. Prioritize discovery and upgrade planning for public Apache-hosted CodeIgniter 3.1.3 applications, but do not classify it as emergency exploitation without additional evidence.
Technical view
CVE-2017-1000247 concerns HTTP header injection in CodeIgniter 3.1.3, specifically the common set_status_header() function under Apache. The likely risk is response-header manipulation where application behavior allows unsafe status header construction. The sources do not provide payload details, affected CPEs, CWE mapping, or exploit confirmation.
Likely exposure
Exposure appears limited to applications running CodeIgniter 3.1.3 under Apache. The bundle lists affected vendor/product metadata as unavailable, so teams must verify framework version and deployment stack directly.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. Public evidence here establishes vulnerability existence, not exploitation prevalence or weaponized availability.
Researcher notes
The source bundle is sparse: no CVSS, CWE, CPE, exploit status, or detailed patch advisory is included. The strongest grounded facts are CodeIgniter 3.1.3, Apache context, set_status_header(), and HTTP header injection. Validate locally before broad conclusions.
Mitigation direction
- Inventory applications using CodeIgniter 3.1.3 under Apache.
- Review the CodeIgniter 3.1.4 changelog and vendor guidance.
- Upgrade affected applications to the vendor-recommended fixed version.
- Prioritize internet-facing applications and authentication-sensitive flows.
- Avoid request-derived values in status-header handling until remediated.
Validation and detection
- Confirm the deployed CodeIgniter framework version for each application.
- Confirm whether the application is served through Apache.
- Search code for direct or indirect set_status_header() usage.
- Check whether status-header values can include user-controlled input.
- Verify remediation against vendor release notes after upgrade.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-1000247 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.codeigniter.com/userguide3/changelog.html#version-3-1-4CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.