CodeIgniter up to 3.1.8 Session Library session fixiation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in CodeIgniter up to 3.1.8. This impacts an unknown function of the component Session Library. The manipulation leads to session fixiation. This vulnerability is referenced as CVE-2018-12071. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in CodeIgniter up to 3.1.8. It has been rated as critical. This issue affects an unknown functionality of the component Session Library. The manipulation with an unknown input leads to a session fixiation vulnerability. Using CWE to declare the problem leads to CWE-384. Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.
The bug was discovered 06/12/2018. The weakness was published 06/17/2018 (Website). The advisory is shared at codeigniter.com. The identification of this vulnerability is CVE-2018-12071 since 06/08/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 3.1.9 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-3879). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Session fixiationCWE: CWE-384
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: CodeIgniter 3.1.9
Timeline
06/08/2018 🔍06/12/2018 🔍
06/17/2018 🔍
06/17/2018 🔍
06/18/2018 🔍
06/09/2025 🔍
Sources
Advisory: codeigniter.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2018-12071 (🔍)
GCVE (CVE): GCVE-0-2018-12071
GCVE (VulDB): GCVE-100-119645
EUVD: 🔍
Entry
Created: 06/18/2018 08:56Updated: 06/09/2025 10:54
Changes: 06/18/2018 08:56 (58), 02/20/2020 08:41 (2), 06/09/2025 09:07 (19), 06/09/2025 10:54 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.