SQL injection via unescaped probe identifiers
Published May 31, 2023 · Updated Jan 9, 2025
SQL injection in MegaEase EaseProbe before 2.1.0 allows local users to alter MySQL or PostgreSQL queries through probe data settings. The MySQL and PostgreSQL getSQL methods split each data-check key into database, table, column, key, and value fields, then interpolate the fields into SQL without neutralizing quotes or identifier syntax. Exploitation requires administrative control of an EaseProbe configuration containing a database client data check and executes with the configured database account's permissions.
Summary
What happened
SQL injection in MegaEase EaseProbe before 2.1.0 allows local users to alter MySQL or PostgreSQL queries through probe data settings. The MySQL and PostgreSQL getSQL methods split each data-check key into database, table, column, key, and value fields, then interpolate the fields into SQL without neutralizing quotes or identifier syntax. Exploitation requires administrative control of an EaseProbe configuration containing a database client data check and executes with the configured database account's permissions.
The record
- CVE
- CVE-2023-33967
- Published
- May 31, 2023
- Updated
- Jan 9, 2025
- Vendor
- MegaEase
- Product
- EaseProbe
- Classifications
- CWE-89
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 31, 2023CVE publishedPublication date reported by the CVE source.
- Jan 9, 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=< 2.1.0
What conditions does exploitation require?
What is affected?
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