Unauthenticated SQL injection via login parameter
Published Jan 31, 2023 · Updated Mar 27, 2025
SQL injection in EQ 1.5.31 through 2.2.0 allows remote attackers to execute database queries through the login request's UserPwd parameter. The login handler executes crafted credential data as SQL: the published proof of concept injects UserNumber, although the CVE record names UserPwd. Authentication is not required, and the demonstrated request induces a five-second database delay without establishing data extraction or modification.
Summary
What happened
SQL injection in EQ 1.5.31 through 2.2.0 allows remote attackers to execute database queries through the login request's UserPwd parameter. The login handler executes crafted credential data as SQL: the published proof of concept injects UserNumber, although the CVE record names UserPwd. Authentication is not required, and the demonstrated request induces a five-second database delay without establishing data extraction or modification.
The record
- CVE
- CVE-2022-45297
- Published
- Jan 31, 2023
- Updated
- Mar 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2023CVE publishedPublication date reported by the CVE source.
- Mar 27, 2025Record 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.
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
- EQ Account/Login time-delay SQL injection proof of conceptproof of concept · demonstrated
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