Device takeover via static maintenance credentials
Published Jun 1, 2023 · Updated Jan 10, 2025
Hard-coded credentials in Sprecher Automation SPRECON-E CPU modules allow remote attackers to take control through enabled maintenance logins. The devices accept two fixed vendor accounts, sprecon and spradm, whose password hashes are shipped in firmware and cannot be changed or deleted. Exploitation requires maintenance access to be enabled; the accounts have limited privileges, and firmware 8.71g adds two-factor authentication.
Summary
What happened
Hard-coded credentials in Sprecher Automation SPRECON-E CPU modules allow remote attackers to take control through enabled maintenance logins. The devices accept two fixed vendor accounts, sprecon and spradm, whose password hashes are shipped in firmware and cannot be changed or deleted. Exploitation requires maintenance access to be enabled; the accounts have limited privileges, and firmware 8.71g adds two-factor authentication.
The record
- CVE
- CVE-2022-4333
- Published
- Jun 1, 2023
- Updated
- Jan 10, 2025
- Vendor
- Sprecher Automation
- Product
- SPRECON-E CPU MC33/34
- Classifications
- CWE-798, CAPEC-21, T0859
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2023CVE publishedPublication date reported by the CVE source.
- Jan 10, 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
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
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