# CVE-2022-4332: Sprecher: Vulnerable firmware verification

> Attackers with physical access can bypass firmware verification to execute arbitrary code and gain full control of the device.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2023
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-73v7-m7qm-qq9g

## What is CVE-2022-4332?

CVE-2022-4332 is a medium-severity vulnerability in Sprecher Automation SPRECON-E-C/P/T3 CPU PU244x, published on 1 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Sprecher Automation SPRECON-E-C/P/T3 CPU in variant PU244x a vulnerable firmware verification has been identified. Through physical access and hardware manipulation, an attacker might be able to bypass hardware-based code verification and thus inject and execute arbitrary code and gain full access of the device.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 6 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.

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

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

## Is CVE-2022-4332 being exploited?

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

## Other vulnerabilities in Sprecher Automation SPRECON-E-C/P/T3 CPU PU244x

- [CVE-2025-41742](https://insights.sbomify.com/CVE-2025-41742/): Hardcoded credentials in SPRECON-E-C (critical 9.8)
- [CVE-2022-4333](https://insights.sbomify.com/CVE-2022-4333/): Sprecher: Sprecon maintenance access with hardcoded credentials (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-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-4332 and fix it if it is affected.

What it is: CVE-2022-4332 is a medium-severity vulnerability in Sprecher Automation SPRECON-E-C/P/T3 CPU PU244x, published on 1 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4332 in the wild and no public exploit code.

Affected product: Sprecher Automation SPRECON-E-C/P/T3 CPU PU244x. 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-4332/ (Markdown: https://insights.sbomify.com/CVE-2022-4332/index.md)
```

## Sources

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

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