Database disclosure via injectable patient-history identifier
Published Jun 14, 2022 · Updated Aug 3, 2024
SQL injection in Hospital's Patient Records Management System 1.0 allows remote authenticated users to read database data via an HTTP POST. The delete_patient_history action accepts the POST id value as SQL syntax; an updatexml payload extracts the active database name through an error. A valid backend session is required; the published proof uses administrator credentials and demonstrates database-name disclosure rather than code execution.
Summary
What happened
SQL injection in Hospital's Patient Records Management System 1.0 allows remote authenticated users to read database data via an HTTP POST. The delete_patient_history action accepts the POST id value as SQL syntax; an updatexml payload extracts the active database name through an error. A valid backend session is required; the published proof uses administrator credentials and demonstrates database-name disclosure rather than code execution.
The record
- CVE
- CVE-2022-32349
- Published
- Jun 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 14, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- SQLi-14 authenticated updatexml proofproof of concept · 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