SQL injection via client-controlled field names
Published Oct 7, 2022 · Updated Aug 3, 2024
Disputed SQL injection in CodeIgniter 3.1.13 and earlier allows remote attackers to alter database queries through a client-controlled field name. The or_like() path delegates to _like(), which interpolates the supplied field key into a LIKE condition while separately escaping only the match value. Exposure requires application code to pass a client-controlled field name into or_like(); multiple third parties dispute that this constitutes a framework vulnerability.
Summary
What happened
Disputed SQL injection in CodeIgniter 3.1.13 and earlier allows remote attackers to alter database queries through a client-controlled field name. The or_like() path delegates to _like(), which interpolates the supplied field key into a LIKE condition while separately escaping only the match value. Exposure requires application code to pass a client-controlled field name into or_like(); multiple third parties dispute that this constitutes a framework vulnerability.
The record
- CVE
- CVE-2022-40829
- 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