Skip to content
Fencer Vulns
medium 4.7

CVE-2023-42811 json

AEADs/aes-gcm: Plaintext exposed in decrypt_in_place_detached even on tag verification failure

published 2023-09-22 3 y ago modified 2026-10-12 27 d ago also GHSA-423w-p2w9-r7vq , RUSTSEC-2023-0096 , EUVD-2023-2411

cvss
4.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

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.

Patch / fix

  • crates.io aes-gcm 0.10.3
  • aes-gcm_project aes-gcm 0.10.3
  • rage-encryption SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 0.9.2+0-150500.3.3.1

suse advisories SUSE-SU-2023:4060-1

  • shadowsocks-rust openSUSE Tumbleweed 1.16.2-1.1

opensuse advisories openSUSE-SU-2024:13315-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-42811 updated cvss 4.7

aes-gcm: Plaintext exposed in decrypt_in_place_detached even on tag verification failure

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/RustCrypto/AEADs/security/advisories/GHSA-423w-p2w9-r7vq referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:N
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:N
OSV 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:N

Affected packages

ecosystem package affected fixed in
crates.io aes-gcm
>=0.10.0, <0.10.3
0.10.3

Affected products

  • RustCrypto AEADs

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.