# CVE-2022-4333: Sprecher: Sprecon maintenance access with hardcoded credentials

> Remote attackers can take over SPRECON-E CPU devices using hardcoded maintenance credentials, requiring deactivation of these accounts.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2023
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-539f-5h6r-p5pf

## What is CVE-2022-4333?

CVE-2022-4333 is a critical vulnerability in Sprecher Automation SPRECON-E CPU MC33/34, published on 1 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hardcoded Credentials in multiple SPRECON-E CPU variants of Sprecher Automation allows an remote attacker to take over the device. These accounts should be deactivated according to Sprecher's hardening guidelines.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-4333?

It affects 9 products.


Products: Sprecher-Automation Sprecon-E-C Firmware, Sprecher-Automation Sprecon-E-P Dl6-1 Firmware, Sprecher-Automation Sprecon-E-P Dq6-1 Firmware, Sprecher-Automation Sprecon-E-P Ds6-0 Firmware, Sprecher-Automation Sprecon-E-T3 Firmware, Sprecher-Automation Sprecon-E-Tc Ax-3110 Firmware, Sprecher-Automation Sprecon-E Ap-2200 Firmware, Sprecher-Automation Sprecon-E Cp-2131 Firmware, Sprecher-Automation Sprecon-E Cp-2330 Firmware.

## How do I fix CVE-2022-4333?

No fix has been published for CVE-2022-4333 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-4333 being exploited?

There is no known exploitation of CVE-2022-4333 in the wild and no public exploit code.

## Other vulnerabilities in Sprecher Automation SPRECON-E CPU MC33/34

- [CVE-2025-41742](https://insights.sbomify.com/CVE-2025-41742/): Hardcoded credentials in SPRECON-E-C (critical 9.8)
- [CVE-2025-41744](https://insights.sbomify.com/CVE-2025-41744/): Sprecher Automation: SPRECON-E series has static default key material for TLS connections (critical 9.1)
- [CVE-2022-4332](https://insights.sbomify.com/CVE-2022-4332/): Sprecher: Vulnerable firmware verification (medium 6.8)
- [CVE-2024-6758](https://insights.sbomify.com/CVE-2024-6758/): Improper Privilege Management vulnerability in Sprecher Automation SPRECON-E (medium 6.5)
- [CVE-2025-41743](https://insights.sbomify.com/CVE-2025-41743/): Sprecher Automation: SPRECON-E series prone to weak encryption of update files (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4333 and fix it if it is affected.

What it is: CVE-2022-4333 is a critical vulnerability in Sprecher Automation SPRECON-E CPU MC33/34, published on 1 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4333 in the wild and no public exploit code.

Affected product: Sprecher Automation SPRECON-E CPU MC33/34. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-4333/ (Markdown: https://insights.sbomify.com/CVE-2022-4333/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4333
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4333
- OSV: https://osv.dev/vulnerability/CVE-2022-4333

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4333/
Summaries are generated and may contain mistakes; the official description above is the record.