SystemSoftware V/KSS: Missing Authentication for Critical Functionality
CVE-2022-2242 is a critical-severity missing authentication for critical functionality vulnerability in SystemSoftware V/KSS from KUKA, with a CVSS 3.1 base score of 9.8 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 8.6.5 as the first without the flaw, so updating SystemSoftware V/KSS to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.22% chance of exploitation within 30 days, higher than 69% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update SystemSoftware V/KSS to 8.6.5 or a later version.
- Read the advisory on kuka.com for workarounds and exact fixed builds.
- 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 |
|---|---|---|---|
| KUKA | SystemSoftware V/KSS | 8.2 up to, but not including, 8.6.5 | 8.6.5 |
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
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (cert.vde.com).
Official description
The KUKA SystemSoftware V/KSS in versions prior to 8.6.5 is prone to improper access control as an unauthorized attacker can directly read and write robot configurations when access control is not available or not enabled (default).
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- kuka.com/advisories-CVE-2022-2242Mitigation
Recent Missing Authentication for Critical Functionality vulnerabilities
- 9.8 Critical severity
- 7.5 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.8 High severity
- 9.1 Critical severity
Spotted an error? Tell us.