CVE-2023-6129: POLY1305 MAC implementation corrupts vector registers on PowerPC

Published Jan 9, 2024
·
Updated

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.

Other sources

OpenSSL is vulnerable to a denial of service, caused by a flaw in the POLY1305 MAC (message authentication code) implementation. By sending a specially crafted request, a remote attacker could exploit this vulnerability to cause a denial of service condition.

IBM

POLY1305 MAC implementation corrupts vector registers on PowerPC

Microsoft

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.

OpenSSL versions 3.0.0 to 3.0.12, 3.1.0 to 3.1.4 and 3.2.0 are vulnerable to this issue. The FIPS provider is not affected because the POLY1305 MAC algorithm is not FIPS approved and the FIPS provider does not implement it.

OpenSSL versions 1.1.1 and 1.0.2 are not affected by this issue.

http://www.openwall.com/lists/oss-security/2024/01/09/1 https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35 https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04 https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015 https://www.openssl.org/news/secadv/20240109.txt

Red Hat

Affected Software

19 affected componentsFixes available
OpenSSL OpenSSL>=3.0.0<=3.0.12
OpenSSL OpenSSL>=3.1.0<=3.1.4
OpenSSL OpenSSL=3.2.0
debian/openssl
1.1.1w-0+deb11u11.1.1w-0+deb11u23.0.15-1~deb12u13.0.14-1~deb12u23.5.0-1
redhat/OpenSSL<3.0
3.0
redhat/OpenSSL<3.2
3.2
IBM QRadar Network Packet Capture<=7.5.0 - 7.5.0 Update Package 7
Microsoft cbl2 cloud-hypervisor-cvm 38.0.72-1
Microsoft azl3 cloud-hypervisor-cvm 38.0.72-2
Microsoft cbl2 hvloader 1.0.1-5
Microsoft azl3 nodejs 20.10.0-2
Microsoft cbl2 hvloader 1.0.1-5
Microsoft cbl2 cloud-hypervisor-cvm 38.0.72.2-1
Microsoft azl3 openssl 3.1.4-9
Microsoft azl3 cloud-hypervisor-cvm 38.0.72.2-1
Microsoft azl3 openssl 3.3.0-1
Microsoft cbl2 hvloader 1.0.1-6
Microsoft azl3 nodejs 20.14.0-1
Microsoft azl3 edk2 20240524git3e722403cd16-8

Event History

Jan 9, 2024
CVE Published
via MITRE·04:36 PM
Data Sourced
via MITRE·04:36 PM
DescriptionWeakness
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 10, 2024
Data Sourced
via Red Hat·05:01 AM
DescriptionSeverityAffected Software
Jan 16, 2024
Data Sourced
via Microsoft·12:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:00 AM
SeverityAffected Software
Updated
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Description
May 31, 2024
Data Sourced
via Launchpad·01:29 PM
Description
Jul 23, 2024
Data Sourced
via IBM·12:00 AM
DescriptionSeverityAffected Software
Sep 16, 2024
Data Sourced
via Ubuntu·01:45 PM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2023-6129?

CVE-2023-6129 is categorized with high severity due to its potential to corrupt application state on PowerPC CPU based platforms.

2

How do I fix CVE-2023-6129?

To mitigate CVE-2023-6129, update to the patched versions of OpenSSL or IBM Cognos Analytics as specified in the vendor advisories.

3

What versions of OpenSSL are affected by CVE-2023-6129?

CVE-2023-6129 affects OpenSSL versions prior to 3.0.12 and 3.1.4.

4

Which IBM Cognos Analytics versions are vulnerable to CVE-2023-6129?

IBM Cognos Analytics versions 12.0.0 to 12.0.3 and 11.2.0 to 11.2.4 FP4 are vulnerable to CVE-2023-6129.

5

What platforms are impacted by CVE-2023-6129?

CVE-2023-6129 impacts applications running on PowerPC CPU based platforms that utilize the POLY1305 MAC implementation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203