CodeIgniter4: Improper Authentication
CVE-2022-46170 is a critical-severity improper authentication vulnerability in CodeIgniter4, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected CodeIgniter4 versions: < 4.2.11. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.91% chance of exploitation within 30 days, higher than 61% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Codeigniter to 4.2.11 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Codeigniter4 | CodeIgniter4 | < 4.2.11 | Not stated |
| Codeigniter | Codeigniter | 4.0.0 up to, but not including, 4.2.11 | 4.2.11 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.6 | High | CNA (github.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
CodeIgniter is a PHP full-stack web framework. When an application uses (1) multiple session cookies (e.g., one for user pages and one for admin pages) and (2) a session handler is set to `DatabaseHandler`, `MemcachedHandler`, or `RedisHandler`, then if an attacker gets one session cookie (e.g., one for user pages), they may be able to access pages that require another session cookie (e.g., for admin pages). This issue has been patched, please upgrade to version 4.2.11 or later. As a workaround, use only one session cookie.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/codeigniter4/CodeIgniter4/security/advisories/GHSA-6cq5-8cj7-g558Third Party Advisory
Patches and release notes
Other vulnerabilities in CodeIgniter4
- 9.8 Critical severity
- 7.5 High severity
- 9.4 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
Recent Improper Authentication vulnerabilities
- 9.8 Critical severity
- 7.5 High severity
- 8.8 High severity
- 9.1 Critical severity
- 9.1 Critical severity
- 7.5 High severity
Spotted an error? Tell us.