CyberSecBulletin
CVE-2022-4333NVD status: Modified

SPRECON-E CPU PU243x: Use of Hard-coded Credentials

CVE-2022-4333 is a critical-severity use of hard-coded credentials vulnerability in SPRECON-E CPU PU243x from Sprecher-automation, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected SPRECON-E CPU PU243x versions: all. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.86% chance of exploitation within 30 days, higher than 59% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Check which version of SPRECON-E CPU PU243x you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on sprecher-automation.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Sprecher AutomationSPRECON-E CPU PU243xallNot stated
Sprecher AutomationSPRECON-E CPU PU244xallNot stated
Sprecher AutomationSPRECON-E CPU MC33/34allNot stated
Sprecher AutomationSPRECON-E CPU SPRECON-EDIRallNot stated
Sprecher-automationSprecon-e-p Dq6-1 FirmwareNot specified in the recordNot stated
Sprecher-automationSprecon-e-p Dl6-1 FirmwareNot specified in the recordNot stated
Sprecher-automationSprecon-e-p Ds6-0 FirmwareNot specified in the recordNot stated
Sprecher-automationSprecon-e-c FirmwareNot specified in the recordNot stated
Sprecher-automationSprecon-e-t3 FirmwareNot specified in the recordNot stated
Sprecher-automationSprecon-e-tc Ax-3110 FirmwareNot specified in the recordNot stated
Sprecher-automationSprecon-e Ap-2200 FirmwareNot specified in the recordNot stated
Sprecher-automationSprecon-e Cp-2131 FirmwareNot specified in the recordNot stated
Sprecher-automationSprecon-e Cp-2330 FirmwareNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (cert.vde.com).

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of Hard-coded Credentials

The product contains hard-coded credentials, such as a password or cryptographic key.

How developers prevent this class of flaw

  • For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible. In Windows environments, the Encrypted File System (EFS) may provide some protection.
  • For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a first login mode that requires the user to enter a unique strong password or key.
  • If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.

More Use of Hard-coded Credentials vulnerabilities (CWE-798)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Use of Hard-coded Credentials vulnerabilities

Spotted an error? Tell us.