CVE-2021-22170

Encrypted-data disclosure via static AES-GCM nonce reuse

Published Dec 6, 2021 · Updated Aug 3, 2024

Cryptographic nonce reuse in GitLab allows attackers with a database copy to decrypt some sensitive encrypted database content. Gitlab::CryptoHelper configures AES-GCM with a static IV derived from the same db_key_base secret as its static key, reusing the key-nonce pair across token values. Exploitation requires a breached database and a known plaintext/ciphertext pair, and it exposes only values protected by the reused keystream.

CVSS severity6.2
Medium
EPSS probability0.54%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cryptographic nonce reuse in GitLab allows attackers with a database copy to decrypt some sensitive encrypted database content. Gitlab::CryptoHelper configures AES-GCM with a static IV derived from the same db_key_base secret as its static key, reusing the key-nonce pair across token values. Exploitation requires a breached database and a known plaintext/ciphertext pair, and it exposes only values protected by the reused keystream.

The record

CVE
CVE-2021-22170
Published
Dec 6, 2021
Updated
Aug 3, 2024
Vendor
GitLab
Product
GitLab
Classifications
CWE-327, T1140
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Dec 6, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>=11.6.0, <13.5.6
  2. Affected versionversion=>=13.6.0, <13.6.4
  3. Affected versionversion=>=13.7.0, <13.7.2

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

GitLab · GitLabversion=>=11.6.0, <13.5.6; version=>=13.6.0, <13.6.4; version=>=13.7.0, <13.7.2

Published CVSS scores

7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
6.2GitLab Inc.CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
5.0NIST NVDAV:N/AC:L/Au:N/C:P/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-327Use of a Broken or Risky Cryptographic Algorithm
T1140Deobfuscate/Decode Files or Information

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo