Unauthenticated REST API control via blank credentials
Published May 25, 2022 · Updated Sep 16, 2024
Authentication bypass in Open Automation Software OAS Platform 16.00.0121 allows remote attackers to control the REST API. The default-enabled API on port 58725 accepts blank credentials at /OASREST/v2/authenticate and returns a token that authorizes configuration operations. No prior account or user interaction is required; the token can read users and security settings, create higher-privileged accounts, and change service ports.
Summary
What happened
Authentication bypass in Open Automation Software OAS Platform 16.00.0121 allows remote attackers to control the REST API. The default-enabled API on port 58725 accepts blank credentials at /OASREST/v2/authenticate and returns a token that authorizes configuration operations. No prior account or user interaction is required; the token can read users and security settings, create higher-privileged accounts, and change service ports.
The record
- CVE
- CVE-2022-26833
- Published
- May 25, 2022
- Updated
- Sep 16, 2024
- Vendor
- Open Automation Software
- Product
- OAS Platform
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 25, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=V16.00.0121
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
- Cisco Talos blank-credential REST API requestproof 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