dbcve.org
Sprecon E P Dq6 1 FirmwareOperating system · Sprecher Automation

CVE-2022-4332

MEDIUM · 6.8 CVSS v3.1 Published 2023-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The SPRECON-E-C/P/T3 CPU (PU244x variant) contains a flawed firmware verification mechanism. An attacker with physical access and the ability to perform hardware manipulation can circumvent the hardware-based code verification, enabling injection and execution of arbitrary code with full device control.

MitigationLimit physical access to the device through secure facility controls, implement tamper-evident hardware seals, and apply vendor firmware updates that address the verification bypass when released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sprecon E P Dq6 1 FirmwareOperating system
Affected:all versions
Sprecon E P Dl6 1 FirmwareOperating system
Affected:all versions
Sprecon E P Ds6 0 FirmwareOperating system
Affected:all versions
Sprecon E C FirmwareOperating system
Affected:all versions
Sprecon E T3 FirmwareOperating system
Affected:all versions
Sprecon E Tc Ax 3110 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Locate the CPU model label on the SPRECON-E hardware. Confirm it is a PU244x variant. Check product documentation or management interface for exact model designation (e.g., Sprecon E P Dq6, Sprecon E P Dl6, Sprecon E P Ds6, Sprecon E C, Sprecon E T3, or Sprecon E Tc Ax 3110).
    Affected if The device is any of the listed affected models (PU244x variant with any of the six firmware designations).
  2. Confirm the firmware version
    Access the device management interface or use the vendor-provided configuration software to retrieve the current firmware version. Look for firmware version information in the system status or about section.
    Affected if All firmware versions are affected per the CVE, so any version confirms the device falls within the vulnerable scope.
  3. Check firmware verification status
    If accessible through the device management interface or diagnostic tools, inspect the firmware verification or code signing status. Look for settings related to 'secure boot', 'code verification', or 'firmware integrity check'.
    Affected if The verification mechanism is flawed by design; the absence or disablement of verification indicates the device is vulnerable.
  4. Inspect for physical tampering indicators
    Examine the device chassis, PCB, and firmware flash chips for signs of physical manipulation. Check for broken seals, unusual solder points, modified components, or devices connected to debug interfaces (JTAG, UART).
    Affected if Evidence of physical access or hardware manipulation suggests the bypass may have been exploited.
  5. Review firmware hash or signature
    If firmware image files are accessible, compute the cryptographic hash and compare against known-good values if available from the vendor. Check whether the firmware includes a valid digital signature.
    Affected if The firmware lacks a valid signature or hash verification, indicating the verification bypass could be present.

If the device is any SPRECON-E model listed in the affected products with any firmware version and the firmware verification mechanism is absent, disabled, or shows signs of tampering, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Limit physical access to the device through secure facility controls, implement tamper-evident hardware seals, and apply vendor firmware updates that address the verification bypass when released.

Fix this in Sprecon E P Dq6 1 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-4332 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-4332 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data