Unauthenticated database disclosure via s_name SQL injection
Published Jan 14, 2025 · Updated Feb 3, 2025
SQL injection in MSFM before 2025.01.01 allows remote attackers to read database data through the s_name parameter at table/list. The table/list handler incorporates the untrusted s_name value into a database query without adequately neutralizing SQL syntax. No authentication or user interaction is required, and the published impact is limited to database confidentiality.
Summary
What happened
SQL injection in MSFM before 2025.01.01 allows remote attackers to read database data through the s_name parameter at table/list. The table/list handler incorporates the untrusted s_name value into a database query without adequately neutralizing SQL syntax. No authentication or user interaction is required, and the published impact is limited to database confidentiality.
The record
- CVE
- CVE-2024-57765
- Published
- Jan 14, 2025
- Updated
- Feb 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2025CVE publishedPublication date reported by the CVE source.
- Feb 3, 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.
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
- Gitee proof of concept for CVE-2024-57765proof of concept · unverified
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