Unauthenticated sensitive-folder access via hard-coded credentials
Published May 26, 2022 · Updated Apr 16, 2025
Use of hard-coded credentials in KUKA KR C4 before 8.7 and KSS all versions allows remote attackers to access sensitive folders. The advisory identifies embedded credentials as the authentication failure but does not name the account, service, or folder paths that accept them. Network reachability is sufficient without authentication; documented impact includes reading, writing, and deleting sensitive files, which can enable unauthorized control-system access.
Summary
What happened
Use of hard-coded credentials in KUKA KR C4 before 8.7 and KSS all versions allows remote attackers to access sensitive folders. The advisory identifies embedded credentials as the authentication failure but does not name the account, service, or folder paths that accept them. Network reachability is sufficient without authentication; documented impact includes reading, writing, and deleting sensitive files, which can enable unauthorized control-system access.
The record
- CVE
- CVE-2021-33016
- Published
- May 26, 2022
- Updated
- Apr 16, 2025
- Vendor
- KUKA
- Product
- KR C4
- Classifications
- CWE-798, T1078.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 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=All <v8.7
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
No public exploit references are available in this record.
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