Local authentication bypass via Project.xml manipulation
Published Sep 15, 2023 · Updated Aug 2, 2024
Improper authentication in SUPCON InPlant SCADA 20230901 allows local users to gain unauthorized access by altering Project.xml. The public record does not identify the function or authentication operation that consumes the altered file. Local access to the project file is required; published assessments bound the consequence to unauthorized access affecting protected SCADA data and operation.
Summary
What happened
Improper authentication in SUPCON InPlant SCADA 20230901 allows local users to gain unauthorized access by altering Project.xml. The public record does not identify the function or authentication operation that consumes the altered file. Local access to the project file is required; published assessments bound the consequence to unauthorized access affecting protected SCADA data and operation.
The record
- CVE
- CVE-2023-4985
- Published
- Sep 15, 2023
- Updated
- Aug 2, 2024
- Vendor
- SUPCON Technology Co., Ltd.
- Product
- InPlant SCADA
- Classifications
- CWE-287, T1556
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=20230901
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.
Public exploit references
- Public Project.xml proof of conceptproof 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