Lucene search

OpensslCVE-2023-6129

HistoryJan 09, 2024 - 5:15 p.m.

CVE-2023-6129

2024-01-0917:15:12

CWE-787

openssl

web.nvd.nist.gov

cve-2023-6129

poly1305

message authentication code

openssl

powerpc cpu

security vulnerability

chacha20-poly1305

aead

tls protocol

nvd

cybersecurity

CVSS3

6.5

Attack Vector

NETWORK

Attack Complexity

HIGH

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

NONE

Integrity Impact

LOW

Availability Impact

HIGH

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

AI Score

6.8

Confidence

High

EPSS

0.002

Percentile

52.7%

JSON

Issue summary: The POLY1305 MAC (message authentication code) implementation
contains a bug that might corrupt the internal state of applications running
on PowerPC CPU based platforms if the CPU provides vector instructions.

Impact summary: If an attacker can influence whether the POLY1305 MAC
algorithm is used, the application state might be corrupted with various
application dependent consequences.

The POLY1305 MAC (message authentication code) implementation in OpenSSL for
PowerPC CPUs restores the contents of vector registers in a different order
than they are saved. Thus the contents of some of these vector registers
are corrupted when returning to the caller. The vulnerable code is used only
on newer PowerPC processors supporting the PowerISA 2.07 instructions.

The consequences of this kind of internal application state corruption can
be various - from no consequences, if the calling application does not
depend on the contents of non-volatile XMM registers at all, to the worst
consequences, where the attacker could get complete control of the application
process. However unless the compiler uses the vector registers for storing
pointers, the most likely consequence, if any, would be an incorrect result
of some application dependent calculations or a crash leading to a denial of
service.

The POLY1305 MAC algorithm is most frequently used as part of the
CHACHA20-POLY1305 AEAD (authenticated encryption with associated data)
algorithm. The most common usage of this AEAD cipher is with TLS protocol
versions 1.2 and 1.3. If this cipher is enabled on the server a malicious
client can influence whether this AEAD cipher is used. This implies that
TLS server applications using OpenSSL can be potentially impacted. However
we are currently not aware of any concrete application that would be affected
by this issue therefore we consider this a Low severity security issue.

Affected configurations

Nvd

Node

opensslopensslRange3.0.0–3.0.12

opensslopensslRange3.1.0–3.1.4

opensslopensslMatch3.2.0

VendorProductVersionCPE
opensslopenssl3.2.0cpe:/a:openssl:openssl:3.2.0:::
opensslopensslcpe:/a:openssl:openssl::::

Vendor	Product	Version	CPE
openssl	openssl	3.2.0	cpe:/a:openssl:openssl:3.2.0:::
openssl	openssl		cpe:/a:openssl:openssl::::

CNA Affected

[
  {
    "defaultStatus": "unaffected",
    "product": "OpenSSL",
    "vendor": "OpenSSL",
    "versions": [
      {
        "lessThan": "3.2.1",
        "status": "affected",
        "version": "3.2.0",
        "versionType": "semver"
      },
      {
        "lessThan": "3.1.5",
        "status": "affected",
        "version": "3.1.0",
        "versionType": "semver"
      },
      {
        "lessThan": "3.0.13",
        "status": "affected",
        "version": "3.0.0",
        "versionType": "semver"
      }
    ]
  }
]