CyberSecBulletin
CVE-2022-3996NVD status: Modified

OpenSSL: Improper Locking

CVE-2022-3996 is a high-severity improper locking vulnerability in OpenSSL, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 3.0.7 as the first without the flaw, so updating OpenSSL to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.31% chance of exploitation within 30 days, higher than 71% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update OpenSSL to 3.0.7 or a later version.
  2. Read the advisory on openssl.org 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
OpenSSLOpenSSL3.0.0 through 3.0.7; 3.0.0 up to, but not including, 3.0.73.0.7
NetAppontap_9all versionsNot stated
NetAppfas\/aff_baseboard_management_controllerall versionsNot stated
NetAppmanagement_services_for_element_softwareall versionsNot stated
NetAppaltavault_ost_plug-inall versionsNot stated
NetApphci_baseboard_management_controllerall versionsNot stated
NetAppsmi-s_providerall versionsNot 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
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighNVD
CVSS 3.17.5HighCISA (ADP)

Official description

If an X.509 certificate contains a malformed policy constraint and policy processing is enabled, then a write lock will be taken twice recursively. On some operating systems (most widely: Windows) this results in a denial of service when the affected process hangs. Policy processing being enabled on a publicly facing server is not considered to be a common setup. Policy processing is enabled by passing the `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function. Update (31 March 2023): The description of the policy processing enablement was corrected based on CVE-2023-0466.

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

The underlying weakness: Improper Locking

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How developers prevent this class of flaw

  • Use industry standard APIs to implement locking mechanism.

More Improper Locking vulnerabilities (CWE-667)

Timeline

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

References

Other vulnerabilities in OpenSSL

All OpenSSL vulnerabilities

Recent Improper Locking vulnerabilities

Spotted an error? Tell us.