Bug 1201332

Summary: VUL-0: CVE-2022-2097: nodejs: AES OCB fails to encrypt some bytes
Product: [Novell Products] SUSE Security Incidents Reporter: Carlos López <carlos.lopez>
Component: IncidentsAssignee: Adam Majer <amajer>
Status: RESOLVED INVALID QA Contact: Security Team bot <security-team>
Severity: Normal    
Priority: P5 - None CC: meissner
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://smash.suse.de/issue/336540/
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on: 1201099    
Bug Blocks:    

Description Carlos López 2022-07-08 10:43:53 UTC
+++ This bug was initially created as a clone of Bug #1201099 +++

AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed.

Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected.

Impacts:

All versions of the 18.x, 16.x, and 14.x releases lines.

https://nodejs.org/en/blog/vulnerability/july-2022-security-releases/#openssl-aes-ocb-fails-to-encrypt-some-bytes-medium-cve-2022-2097

----------------------------------------
Original OpenSSL advisory
----------------------------------------

AES OCB fails to encrypt some bytes (CVE-2022-2097)

Severity: Moderate

AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimized
implementation will not encrypt the entirety of the data under some
circumstances. This could reveal sixteen bytes of data that was
preexisting in the memory that wasn't written. In the special case of
"in place" encryption, sixteen bytes of the plaintext would be revealed.

Since OpenSSL does not support OCB based cipher suites for TLS and DTLS,
they are both unaffected.

This issue affects versions 1.1.1 and 3.0. It was addressed in the
releases of 1.1.1q and 3.0.5 on the 5th July 2022.

OpenSSL 1.1.1 users should upgrade to 1.1.1q
OpenSSL 3.0 users should upgrade to 3.0.5

This issue was reported to OpenSSL on the 15th June 2022 by Alex
Chernyakhovsky from Google. The fix was developed by Alex Chernyakhovsky,
David Benjamin and Alejandro Sedeño from Google.
Comment 1 Carlos López 2022-07-08 10:53:05 UTC
Upstream nodejs bundles OpenSSL, but we do not, so this is fixed by updating OpenSSL. Closing.