SQL injection via unfiltered database field names
Published Oct 7, 2022 · Updated Aug 3, 2024
The disputed SQL injection claim for CodeIgniter 3.0 through 3.1.13 describes attackers altering queries through database field names. When application code passes client input as a field name, where_in() in system/database/DB_query_builder.php does not filter the identifier before adding it to the SQL query. The report itself makes exploitation conditional on a developer incorrectly accepting query fields from a client, so affected deployments depend on application-specific usage.
Summary
What happened
The disputed SQL injection claim for CodeIgniter 3.0 through 3.1.13 describes attackers altering queries through database field names. When application code passes client input as a field name, where_in() in system/database/DB_query_builder.php does not filter the identifier before adding it to the SQL query. The report itself makes exploitation conditional on a developer incorrectly accepting query fields from a client, so affected deployments depend on application-specific usage.
The record
- CVE
- CVE-2022-40825
- Published
- Oct 7, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89
- 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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