asyncua: Improper Authentication
CVE-2023-26150 is a high-severity improper authentication vulnerability in asyncua, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 0.9.96 as the first without the flaw, so updating asyncua to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.52% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update asyncua to 0.9.96 or a later version.
- Update Opcua-asyncio to 0.9.96 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Asyncua | asyncua | before 0.9.96 | 0.9.96 |
| Freeopcua | Opcua-asyncio | before 0.9.96 | 0.9.96 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.5 | Medium | CNA (snyk.io) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
Versions of the package asyncua before 0.9.96 are vulnerable to Improper Authentication such that it is possible to access Address Space without encryption and authentication. **Note:** This issue is a result of missing checks for services that require an active session.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/FreeOpcUa/opcua-asyncio/commit/2be7ce80df05de8d6c6ae1ebce6fa2bb7147844a
- github.com/FreeOpcUa/opcua-asyncio/commit/b4106dfd5037423c9d1810b48a97296b59cde513
- github.com/FreeOpcUa/opcua-asyncio/pull/1015
- github.com/FreeOpcUa/opcua-asyncio/releases/tag/v0.9.96Product, Release Notes
- security.snyk.io/vuln/SNYK-PYTHON-ASYNCUA-5673435Exploit, Third Party Advisory
Technical write-ups (may include proof of concept)
- gist.github.com/artfire52/84f7279a4119d6f90381ac49d7121121Exploit, Third Party Advisory
- github.com/FreeOpcUa/opcua-asyncio/issues/1014Exploit, Issue Tracking, Third Party Advisory
Other vulnerabilities in asyncua
- 7.5 High severity
- 7.5 High severity
Recent Improper Authentication vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 8.8 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.1 Critical severity
Spotted an error? Tell us.