CodeIgniter4 Potential Session Handlers Vulnerability
Published 22 Dec 2022 · Updated 6 Dec 2023
Affected package
- Affected
- <4.2.11
- Fixed in
- 4.2.11
composer require codeigniter4/framework:^4.2.11Details
Impact
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).
Patches
Upgrade to version 4.2.11 or later.
Workarounds
- Use only one session cookie.
References
- https://codeigniter4.github.io/userguide/libraries/sessions.html#session-drivers
For more information
If you have any questions or comments about this advisory:
- Open an issue in codeigniter4/CodeIgniter4
- Email us at SECURITY.md
Is GHSA-6cq5-8cj7-g558 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected codeigniter4/framework, and gives you the command that fixes it.
References
- Linkgithub.com/codeigniter4/CodeIgniter4/security/advisories/GHSA-6cq5-8cj7-g558
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-46170
- Linkgithub.com/codeigniter4/CodeIgniter4/commit/f9fb6574fbeb5a4aa63f7ea87296523e10db9328
- Linkcodeigniter4.github.io/userguide/libraries/sessions.html#session-drivers
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/codeigniter4/framework/CVE-2022-46170.yaml
- Packagegithub.com/codeigniter4/CodeIgniter4
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.