cve.bz

CVE-2023-42811

5.5 mediumExploit referenceEPSS 0.2%Fix available

Medium (5.5). EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in aes-gcm 0.10.3.

On this page
aes-gcm is a pure Rust implementation of the AES-GCM. Starting in version 0.10.0 and prior to version 0.10.3, in the AES GCM implementation of decrypt_in_place_detached, the decrypted ciphertext (i.e. the correct plaintext) is exposed even if tag verification fails. If a program using the `aes-gcm` crate's `decrypt_in_place*` APIs accesses the buffer after decryption failure, it will contain a decryption of an unauthenticated input. Depending on the specific nature of the program this may enable Chosen Ciphertext Attacks (CCAs) which can cause a catastrophic breakage of the cipher including full plaintext recovery. Version 0.10.3 contains a fix for this issue.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2024-02-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-42811 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-42811?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-42811?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-42811 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
aes-gcm_project:aes-gcmfrom 0.10.0 before 0.10.3
fedoraproject:fedora37
fedoraproject:fedora38
fedoraproject:fedora39

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-423w-p2w9-r7vqcrates.ioaes-gcm>=0.10.0 <0.10.30.10.3
RUSTSEC-2023-0096crates.ioaes-gcm>=0.10.0 <0.10.30.10.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Module for Basesystem 15 SP5rage-encryption0.9.2+0-150500.3.3.1SUSE-SU-2023:4060-1
openSUSELeap 15.5rage-encryption0.9.2+0-150500.3.3.1SUSE-SU-2023:4060-1
openSUSETumbleweedshadowsocks-rust1.16.2-1.1openSUSE-SU-2024:13315-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON