Authenticated SQL injection via unsanitized fileId
Published Oct 31, 2024 · Updated Nov 1, 2024
SQL injection in FileDirectoryService.docHistory in ESAFENET CDG 5 allows remote authenticated users to alter database queries via fileId. The docHistory function incorporates attacker-controlled fileId content into an SQL command without neutralizing SQL syntax. A low-privileged CDG account is required, and successful exploitation can read, modify, or delete data available to the application's database account.
Summary
What happened
SQL injection in FileDirectoryService.docHistory in ESAFENET CDG 5 allows remote authenticated users to alter database queries via fileId. The docHistory function incorporates attacker-controlled fileId content into an SQL command without neutralizing SQL syntax. A low-privileged CDG account is required, and successful exploitation can read, modify, or delete data available to the application's database account.
The record
- CVE
- CVE-2024-10594
- Published
- Oct 31, 2024
- Updated
- Nov 1, 2024
- Vendor
- Beijing Esafenet Technology Development Co., Ltd.
- Product
- CDG
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 31, 2024CVE publishedPublication date reported by the CVE source.
- Nov 1, 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=5
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