CVE-2023-4807 @ Archive

"CVE-2023-4807"
"openssl-1.1.1n-0+deb10u6"
"libxmlsec1-openssl-1.2.27-2"
"Am I vulnerable?"

Status

new

Priority

0.67

Match score

4.0

Risk

DoS priv:user

CVSS

7.8 HIGH

Reason

cpe: openssl; pkgs: openssl; version: in-range: openssl-1.1.1n-0+deb10u6; risk:dos

Created

2026-10-15T10:20:16Z

Updated

2026-10-20T10:18:28Z

Package interrogation (copy)

Run on the host — click to copy a command. Debian/apt

Package	Commands
openssl-1.1.1n-0+deb10u6
libxmlsec1-openssl-1.2.27-2

Inventory lookup

Search package inventory across systems, then return here. Create a ticket on systems the matcher missed.

Suggestions: openssl

Same product CVEs in your queue

Other open tickets that look like the same product. Closed tickets are omitted unless they are already pegged to this CVE.

CVE	CVSS	Systems	Status	Matched	Already related
CVE-2021-20232	9.8	Saiph	new	openssl	—
CVE-2021-20231	9.8	Saiph	new	openssl	—
CVE-2022-0778	7.5	Library, morris, mufasa	new	openssl	—
CVE-2023-0215	7.5	Archive, Janus, Saiph, morris, mufasa	new	openssl	—
CVE-2023-0464	7.5	Archive, Janus, Saiph, morris, mufasa	new	openssl	—
CVE-2024-0553	7.5	Library, Saiph	new	openssl	—
CVE-2020-24659	7.5	Library, Saiph	new	openssl	—
CVE-2022-2509	7.5	Library, Saiph	new	openssl	—
CVE-2022-4450	7.5	Archive, Janus, Saiph	new	openssl	—
CVE-2023-0286	7.4	Archive, Janus, Saiph, morris, mufasa	new	openssl	—
CVE-2020-13777	7.4	Saiph	new	openssl	—
CVE-2022-2068	7.3	Archive, Janus, Saiph, morris, mufasa	new	openssl	—
CVE-2022-1292	7.3	Archive, Janus, Saiph, morris, mufasa	new	openssl	—

Related CVE (same fix)

Point this ticket’s CVE at a higher-priority / same-fix primary so you only triage one.

Host OS / kernel

Debian GNU/Linux 10 (buster) (10) · debian

Arch

x86_64

kernel_release

uname -r → 5.10.0-25-amd64

kernel_version

uname -v → #1 SMP Debian 5.10.191-1 (2023-08-16)

For Linux kernel CVEs, kernel_version (Debian packaging / build string) often decides fixed vs not; kernel_release is used for upstream NVD range compares.

Same CVE on other hosts

Open the ticket for this CVE on another system.

System	Status	Priority	Updated
Janus	new	0.67	2026-10-20T10:18:28Z	Open
Saiph	new	0.67	2026-10-20T10:18:28Z	Open

Description

Issue summary: The POLY1305 MAC (message authentication code) implementation
contains a bug that might corrupt the internal state of applications on the
Windows 64 platform when running on newer X86_64 processors supporting the
AVX512-IFMA instructions.

Impact summary: If in an application that uses the OpenSSL library 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 does
not save the contents of non-volatile XMM registers on Windows 64 platform
when calculating the MAC of data larger than 64 bytes. Before returning to
the caller all the XMM registers are set to zero rather than restoring their
previous content. The vulnerable code is used only on newer x86_64 processors
supporting the AVX512-IFMA 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 given the contents of the registers are just zeroized so
the attacker cannot put arbitrary values inside, 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 and a malicious client can influence whether this AEAD
cipher is used by the server. This implies that 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.

As a workaround the AVX512-IFMA instructions support can be disabled at
runtime by setting the environment variable OPENSSL_ia32cap:

   OPENSSL_ia32cap=:~0x200000

The FIPS provider is not affected by this issue.

Update status

Add note only

References

NVD: CVE-2023-4807