Unauthenticated account creation via SecureAddUser messages
Published May 25, 2022 · Updated Apr 15, 2025
Missing authentication in OAS Platform 16.00.0112 allows remote attackers to create OAS user accounts through network requests. OAS Engine processes properly formatted SecureAddUser and SecureConfigValues messages on its configuration service without authenticating the sender. Network access to TCP port 58727, used by default, is sufficient to create an account and assign a custom security group whose permissions govern subsequent authenticated requests.
Summary
What happened
Missing authentication in OAS Platform 16.00.0112 allows remote attackers to create OAS user accounts through network requests. OAS Engine processes properly formatted SecureAddUser and SecureConfigValues messages on its configuration service without authenticating the sender. Network access to TCP port 58727, used by default, is sufficient to create an account and assign a custom security group whose permissions govern subsequent authenticated requests.
The record
- CVE
- CVE-2022-26303
- Published
- May 25, 2022
- Updated
- Apr 15, 2025
- Vendor
- Open Automation Software
- Product
- OAS Platform
- Classifications
- CWE-306, T1136
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 25, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=V16.00.0112
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.
Public exploit references
- SecureAddUser and SecureConfigValues packet examplesproof 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