Database information disclosure via blind SQL injection
Published Jan 14, 2025 · Updated Jan 14, 2025
SQL injection in Fortinet FortiSIEM 6.4, 6.5, 6.6, 6.7, 7.0, and 7.1 allows remote authenticated users to extract database information. The GUI Update/Create Case feature uses crafted request values in database queries without neutralizing SQL control elements. High-privilege authentication is required, and the blind injection is bounded to reading database information, with no reported write or service-interruption impact.
Summary
What happened
SQL injection in Fortinet FortiSIEM 6.4, 6.5, 6.6, 6.7, 7.0, and 7.1 allows remote authenticated users to extract database information. The GUI Update/Create Case feature uses crafted request values in database queries without neutralizing SQL control elements. High-privilege authentication is required, and the blind injection is bounded to reading database information, with no reported write or service-interruption impact.
The record
- CVE
- CVE-2024-52969
- Published
- Jan 14, 2025
- Updated
- Jan 14, 2025
- Vendor
- Fortinet
- Product
- FortiSIEM
- Classifications
- CWE-89, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 2025CVE publishedPublication date reported by the CVE source.
- Jan 14, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.4.0 <=6.4.4
- Affected versionversion=6.5.0 <=6.5.3
- Affected versionversion=6.6.0 <=6.6.5
- Affected versionversion=6.7.0 <=6.7.9
- Affected versionversion=7.0.0 <=7.0.3
- Affected versionversion=7.1.0 <=7.1.7
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