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.
The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
| Link | Tags |
|---|---|
| https://github.com/codeigniter4/CodeIgniter4/security/advisories/GHSA-745p-r637-7vvp | third party advisory mitigation |
| https://github.com/codeigniter4/CodeIgniter4/issues/6540 | issue tracking exploit third party advisory |
| https://github.com/codeigniter4/CodeIgniter4/pull/6544 | third party advisory patch |
| https://codeigniter4.github.io/userguide/helpers/cookie_helper.html#set_cookie | third party advisory technical description |
| https://codeigniter4.github.io/userguide/outgoing/response.html#CodeIgniter%5CHTTP%5CResponse::setCookie | third party advisory technical description |
| https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#restrict_access_to_cookies | third party advisory technical description |