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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-39284US | medium4.3 | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://codeigniter4.github.io/userguide/helpers/cookie_helper.html#set_cookieWEB
- https://codeigniter4.github.io/userguide/outgoing/response.html#CodeIgniter%5CHTTP%5CResponse::setCookieWEB
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#restrict_access_to_cookiesWEB
- https://github.com/codeigniter4/CodeIgniter4/issues/6540WEB
- https://github.com/codeigniter4/CodeIgniter4/pull/6544WEB
- https://github.com/codeigniter4/CodeIgniter4/security/advisories/GHSA-745p-r637-7vvpWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan