POLY1305 MAC implementation corrupts vector registers on PowerPC (CVE-2023-6129)
Published Last modified Sources: Siemens ProductCERT, BSI, Ubuntu, Msrc Update Guide, EUVD, CVE.org
What is affected, what to do
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.
Update OpenSSL to version 3.2.1, OpenSSL to version 3.1.5, OpenSSL to version 3.0.13.
- Affected
- OpenSSL
lt 3.2.0..3.2.1 - OpenSSL
lt 3.1.0..3.1.5 - OpenSSL
lt 3.0.0..3.0.13
- OpenSSL
- Fixed in
- OpenSSL
3.2.1 - OpenSSL
3.1.5 - OpenSSL
3.0.13
- OpenSSL
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
6.5
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
6.5
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: Siemens ProductCERT, BSI, Ubuntu, Msrc Update Guide, EUVD, CVE.org
2.3 %
EPSS score
Moderate — model estimates 1-10% exploitation likelihood.
Source: FIRST EPSS, percentile 83.5
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 92.45 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 6.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 6.5
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 2.3 %
- Moderate — model estimates 1-10% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 83.5
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 22 January 2024
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-440
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
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.
Source: siemens_advisory, BSI CSAF, BSI WID Portal, Ubuntu Security Notices, Microsoft Security Update Guide, ENISA EUVD, cvelistv5, NVD (NIST)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| OpenSSL | OpenSSL |
|
|
| openssl | openssl |
|
|
| Oracle | JD Edwards |
|
|
Vendors and products
Affected operating systems
| Linux | ubuntu | openssl | focal |
| Linux | ubuntu | openssl | jammy |
| Linux | ubuntu | openssl | mantic |
Weakness classes (CWE)
CWE-440Expected Behavior Violation
Base
A feature, API, or function does not perform according to its specification.
Entry at MITRE CWE-440
References & sources
- openssl.orgOpenSSL Advisoryeuvd, Vendor advisory
- github.com3.2.1 git commiteuvd, Patch
- github.com3.1.5 git commiteuvd, Patch
- github.com3.0.13 git commiteuvd, Patch
- security.netapp.comadvisory/ntap-20240216-0009x_transferred
- security.netapp.comadvisory/ntap-20240426-0013x_transferred
- security.netapp.comadvisory/ntap-20240426-0008x_transferred
- openwall.comlists/oss-security/2024/03/11/1x_transferred
- security.netapp.comadvisory/ntap-20240503-0011x_transferred
- Siemens ProductCERTproductcert/html/ssa-265688.html
- Siemens ProductCERTproductcert/html/ssa-331112.html
- Siemens ProductCERTproductcert/html/ssa-915275.html
- Siemens ProductCERTproductcert/html/ssa-769027.html
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedopenssl.org
New references:Show 12 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35Reference added —https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04Reference added —https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015Reference added —https://www.openssl.org/news/secadv/20240109.txtReference removed https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35—Reference removed https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04—Reference removed https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015—Reference removed https://www.openssl.org/news/secadv/20240109.txt—Reference type removed https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35 Types: Patch—Reference type removed https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04 Types: Patch—Reference type removed https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015 Types: Patch—Reference type removed https://www.openssl.org/news/secadv/20240109.txt Types: Vendor Advisory—Source identifier: openssl-security@openssl.org
Record modifiedCVE Program
New references:- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35
- https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04
- https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015
and 5 more references
Show 22 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —http://www.openwall.com/lists/oss-security/2024/03/11/1Reference added —https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35Reference added —https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04Reference added —https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015Reference added —https://security.netapp.com/advisory/ntap-20240216-0009/Reference added —https://security.netapp.com/advisory/ntap-20240426-0008/Reference added —https://security.netapp.com/advisory/ntap-20240426-0013/Reference added —https://security.netapp.com/advisory/ntap-20240503-0011/Reference added —https://www.openssl.org/news/secadv/20240109.txtReference removed http://www.openwall.com/lists/oss-security/2024/03/11/1—Reference removed https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35—Reference removed https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04—Reference removed https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015—Reference removed https://security.netapp.com/advisory/ntap-20240216-0009/—Reference removed https://security.netapp.com/advisory/ntap-20240426-0008/—Reference removed https://security.netapp.com/advisory/ntap-20240426-0013/—Reference removed https://security.netapp.com/advisory/ntap-20240503-0011/—Reference removed https://www.openssl.org/news/secadv/20240109.txt—Reference type removed https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35 Types: Patch—Reference type removed https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04 Types: Patch—Reference type removed https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015 Types: Patch—Reference type removed https://www.openssl.org/news/secadv/20240109.txt Types: Vendor Advisory—Source identifier: af854a3a-2127-422b-91ae-364da2661108
Record modifiedSiemens ADP
Show 9 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2023/6xxx/CVE-2023-6129.json">CVE-2023-6129</a>Reference added —https://cert-portal.siemens.com/productcert/html/ssa-265688.htmlReference added —https://cert-portal.siemens.com/productcert/html/ssa-331112.htmlReference added —https://cert-portal.siemens.com/productcert/html/ssa-769027.htmlReference added —https://cert-portal.siemens.com/productcert/html/ssa-915275.htmlReference removed https://cert-portal.siemens.com/productcert/html/ssa-265688.html—Reference removed https://cert-portal.siemens.com/productcert/html/ssa-331112.html—Reference removed https://cert-portal.siemens.com/productcert/html/ssa-769027.html—Reference removed https://cert-portal.siemens.com/productcert/html/ssa-915275.html—Source identifier: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2023-6129"><img src="https://intel.neosec.eu/badge/cve/CVE-2023-6129.svg?lang=en" alt="CVE-2023-6129 – NEOSEC Intel" height="20"></a>