CyberSecBulletin
CVE-2023-5363NVD status: Modified

OpenSSL: Incorrect Provision of Specified Functionality

Published Updated By the CyberSecBulletin desk

CVE-2023-5363 is a high-severity incorrect provision of specified functionality 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 versions 3.0.12, 3.1.4 as the first without the flaw, so updating OpenSSL to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 3.94% chance of exploitation within 30 days, which is in the top 9.44% of all scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update OpenSSL to 3.0.12 or 3.1.4, whichever matches your release line, or a later version.
  2. Update SIDIS Prime to V4.0.700 or a later version.
  3. Update SINEC NMS to V3.0 SP1 or a later version.
  4. Read the advisory on git.openssl.org for workarounds and exact fixed builds.
  5. 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 up to, but not including, 3.0.12; 3.1.0 up to, but not including, 3.1.43.0.12, 3.1.4
SiemensSIDIS Primebefore V4.0.700V4.0.700
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFPV3.1.5 and laterNot stated
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFPV3.1.5 and laterNot stated
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFPV3.1.5 and laterNot stated
SiemensSINEC NMSbefore V3.0 SP1V3.0 SP1
DebianDebian Linux12.0Not stated
NetAppH300s FirmwareNot specified in the recordNot stated
NetAppH410s FirmwareNot specified in the recordNot stated
NetAppH500s FirmwareNot specified in the recordNot stated
NetAppH700s FirmwareNot specified in the recordNot stated
NetAppH410c 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
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

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

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

Official description

Issue summary: A bug has been identified in the processing of key and initialisation vector (IV) lengths. This can lead to potential truncation or overruns during the initialisation of some symmetric ciphers. Impact summary: A truncation in the IV can result in non-uniqueness, which could result in loss of confidentiality for some cipher modes. When calling EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() or EVP_CipherInit_ex2() the provided OSSL_PARAM array is processed after the key and IV have been established. Any alterations to the key length, via the "keylen" parameter or the IV length, via the "ivlen" parameter, within the OSSL_PARAM array will not take effect as intended, potentially causing truncation or overreading of these values. The following ciphers and cipher modes are impacted: RC2, RC4, RC5, CCM, GCM and OCB. For the CCM, GCM and OCB cipher modes, truncation of the IV can result in loss of confidentiality. For example, when following NIST's SP 800-38D section 8.2.1 guidance for constructing a deterministic IV for AES in GCM mode, truncation of the counter portion could lead to IV reuse. Both truncations and overruns of the key and overruns of the IV will produce incorrect results and could, in some cases, trigger a memory exception. However, these issues are not currently assessed as security critical. Changing the key and/or IV lengths is not considered to be a common operation and the vulnerable API was recently introduced. Furthermore it is likely that application developers will have spotted this problem during testing since decryption would fail unless both peers in the communication were similarly vulnerable. For these reasons we expect the probability of an application being vulnerable to this to be quite low. However if an application is vulnerable then this issue is considered very serious. For these reasons we have assessed this issue as Moderate severity overall. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this because the issue lies outside of the FIPS provider boundary. OpenSSL 3.1 and 3.0 are vulnerable to this issue.

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

The underlying weakness: Incorrect Provision of Specified Functionality

The code does not function according to its published specifications, potentially leading to incorrect usage.

How developers prevent this class of flaw

  • Ensure that your code strictly conforms to specifications.

More Incorrect Provision of Specified Functionality vulnerabilities (CWE-684)

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 Incorrect Provision of Specified Functionality vulnerabilities

Spotted an error? Tell us.