Database disclosure via unsanitized duplicate-name parameters
Published Mar 3, 2022 · Updated Aug 4, 2024
SQL injection in OS4ED openSIS 8.0 allows remote attackers to extract database information through CheckDuplicateName.php. The endpoint incorporates attacker-controlled table_name, field_name, id, and field_id parameters into SQL processing without sanitization. No authentication or user interaction is required; a crafted GET request can disclose database contents through error-based query output.
Summary
What happened
SQL injection in OS4ED openSIS 8.0 allows remote attackers to extract database information through CheckDuplicateName.php. The endpoint incorporates attacker-controlled table_name, field_name, id, and field_id parameters into SQL processing without sanitization. No authentication or user interaction is required; a crafted GET request can disclose database contents through error-based query output.
The record
- CVE
- CVE-2021-40636
- Published
- Mar 3, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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
- CheckDuplicateName.php error-based SQL injection requestfunctional · 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