CodeIgniter up to 2.2.3 Active Record offset sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in CodeIgniter up to 2.2.3. Affected is an unknown function of the component Active Record Handler. The manipulation of the argument offset as part of Variable leads to sql injection. This vulnerability is documented as CVE-2015-5725. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in CodeIgniter up to 2.2.3. It has been rated as critical. This issue affects some unknown processing of the component Active Record Handler. The manipulation of the argument offset as part of a Variable leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in the offset method in the Active Record class in CodeIgniter before 2.2.4 allows remote attackers to execute arbitrary SQL commands via vectors involving the offset variable.
The bug was discovered 08/20/2015. The weakness was released 02/21/2018 (Website). It is possible to read the advisory at forum.codeigniter.com. The identification of this vulnerability is CVE-2015-5725 since 08/04/2015. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 916 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.2.4 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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 2.2.4
Patch: github.com
Timeline
08/04/2015 🔍08/20/2015 🔍
02/21/2018 🔍
02/21/2018 🔍
02/22/2018 🔍
02/08/2023 🔍
Sources
Advisory: 0dde92def6b9f276f05ff77abb07ead318f9ec23Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-5725 (🔍)
GCVE (CVE): GCVE-0-2015-5725
GCVE (VulDB): GCVE-100-113651
Entry
Created: 02/22/2018 07:27Updated: 02/08/2023 16:28
Changes: 02/22/2018 07:27 (59), 01/07/2020 14:49 (2), 02/08/2023 16:28 (5)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.