SQL injection via caller-controlled field names
Published Oct 7, 2022 · Updated Aug 3, 2024
SQL injection in CodeIgniter 3.1.13 and earlier allows remote attackers to alter database queries through a crafted field name. The where_not_in() path passes its caller-supplied key to _where_in(), which concatenates that key into a NOT IN condition while escaping only the values. Reachability requires an application to accept a client-controlled field name; the upstream issue questions whether that developer misuse constitutes a framework flaw, and the CVE is disputed.
Summary
What happened
SQL injection in CodeIgniter 3.1.13 and earlier allows remote attackers to alter database queries through a crafted field name. The where_not_in() path passes its caller-supplied key to _where_in(), which concatenates that key into a NOT IN condition while escaping only the values. Reachability requires an application to accept a client-controlled field name; the upstream issue questions whether that developer misuse constitutes a framework flaw, and the CVE is disputed.
The record
- CVE
- CVE-2022-40830
- Published
- Oct 7, 2022
- Updated
- Aug 3, 2024
- Vendor
- CodeIgniter Foundation
- Product
- CodeIgniter
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 7, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.1.13
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo