CVE-2022-39284
Summary
| CVE | CVE-2022-39284 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-10-06 20:15:00 UTC |
| Updated | 2023-07-11 20:51:00 UTC |
| Description | CodeIgniter is a PHP full-stack web framework. In versions prior to 4.2.7 setting `$secure` or `$httponly` value to `true` in `Config\Cookie` is not reflected in `set_cookie()` or `Response::setCookie()`. As a result cookie values are erroneously exposed to scripts. It should be noted that this vulnerability does not affect session cookies. Users are advised to upgrade to v4.2.7 or later. Users unable to upgrade are advised to manually construct their cookies either by setting the options in code or by constructing Cookie objects. Examples of each workaround are available in the linked GHSA. |
Risk And Classification
Problem Types: CWE-732
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Codeigniter | Codeigniter | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Cookie Helper — CodeIgniter 4.2.0 documentation | MISC | codeigniter4.github.io | |
| HTTP Responses — CodeIgniter 4.2.0 documentation | MISC | codeigniter4.github.io | |
| Bug: set_cookie not using default value of $secure from config · Issue #6540 · codeigniter4/CodeIgniter4 · GitHub | MISC | github.com | |
| Secure or HttpOnly flag set in Config\Cookie is not reflected in Cookies issued in Codeigniter4 · Advisory · codeigniter4/CodeIgniter4 · GitHub | CONFIRM | github.com | |
| cve-website | MISC | www.cve.org | |
| Using HTTP cookies - HTTP | MDN | MISC | developer.mozilla.org | |
| fix: set_cookie() does not use Config\Cookie values by kenjis · Pull Request #6544 · codeigniter4/CodeIgniter4 · GitHub | MISC | github.com | |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.