Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2020-14382: A vulnerability was found in upstream release cryptsetup-2.2.0 where, there's a bug in LUKS2 format validation code, that is effectively…

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67.4% of all records.
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: cryptsetup (Alpine:v3.11) 2.2.2-r1; cryptsetup (Alpine:v3.12) 2.3.2-r1; cryptsetup (Alpine:v3.13) 2.3.4-r0.

Low priority for now. Upgrade to cryptsetup (Alpine:v3.11) 2.2.2-r1; cryptsetup (Alpine:v3.12) 2.3.2-r1; cryptsetup (Alpine:v3.13) 2.3.4-r0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A vulnerability was found in upstream release cryptsetup-2.2.0 where, there's a bug in LUKS2 format validation code, that is effectively invoked on every device/image presenting itself as LUKS2 container. The bug is in segments validation code in file 'lib/luks2/luks2_json_metadata.c' in function hdr_validate_segments(struct crypt_device *cd, json_object *hdr_jobj) where the code does not check for possible overflow on memory allocation used for intervals array (see statement "intervals = malloc(first_backup * sizeof(*intervals));"). Due to the bug, library can be *tricked* to expect such allocation was successful but for far less memory then originally expected. Later it may read data FROM image crafted by an attacker and actually write such data BEYOND allocated memory.

Published
Sep 16, 2020
Updated
Jun 16, 2026
EPSS
1.1% · 67th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-14382

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for cryptsetup project records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
cryptsetup projectcryptsetup
redhatenterprise linux
canonicalubuntu linux
fedoraprojectfedora

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a cryptsetup

    • cryptsetup-2.2.0affected
Affected versions · NVD (5)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux20.04
  • cryptsetup project cryptsetup2.2.0
  • fedoraproject fedora31
  • fedoraproject fedora33
  • redhat enterprise linux8.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.11cryptsetupbefore 2.2.2-r12.2.2-r1
Alpine:v3.12cryptsetupbefore 2.3.2-r12.3.2-r1
Alpine:v3.13cryptsetupbefore 2.3.4-r02.3.4-r0
Debian:12cryptsetupbefore 2:2.3.4-12:2.3.4-1
openSUSE:Tumbleweedcryptsetupbefore 2.4.1-1.12.4.1-1.1
Red Hat:enterprise_linux:8::appstreamcryptsetup-debuginfobefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::appstreamcryptsetup-debugsourcebefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::appstreamcryptsetup-develbefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::appstreamcryptsetup-libs-debuginfobefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::appstreamcryptsetup-reencrypt-debuginfobefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::appstreamintegritysetup-debuginfobefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::appstreamveritysetup-debuginfobefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::baseoscryptsetupbefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::baseoscryptsetup-libsbefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::baseoscryptsetup-reencryptbefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::baseosintegritysetupbefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:enterprise_linux:8::baseosveritysetupbefore 0:2.3.3-2.el80:2.3.3-2.el8
Red Hat:rhel_eus:8.1::appstreamcryptsetup-debuginfobefore 0:2.2.0-2.el8_1.10:2.2.0-2.el8_1.1
Red Hat:rhel_eus:8.1::appstreamcryptsetup-debugsourcebefore 0:2.2.0-2.el8_1.10:2.2.0-2.el8_1.1
Red Hat:rhel_eus:8.1::appstreamcryptsetup-develbefore 0:2.2.0-2.el8_1.10:2.2.0-2.el8_1.1
Red Hat:rhel_eus:8.1::appstreamcryptsetup-libs-debuginfobefore 0:2.2.0-2.el8_1.10:2.2.0-2.el8_1.1
Red Hat:rhel_eus:8.1::appstreamcryptsetup-reencrypt-debuginfobefore 0:2.2.0-2.el8_1.10:2.2.0-2.el8_1.1
Red Hat:rhel_eus:8.1::appstreamintegritysetup-debuginfobefore 0:2.2.0-2.el8_1.10:2.2.0-2.el8_1.1
Red Hat:rhel_eus:8.1::appstreamveritysetup-debuginfobefore 0:2.2.0-2.el8_1.10:2.2.0-2.el8_1.1

+17

Same product

cryptsetup project: all records

Other highest-scoring records for the same primary product.

  • CVE-2016-4484The Debian initrd script for the cryptsetup package 2:1.7.3-2 and earlier allows physically proximate attackers to gain shell access via…
    27Monitor
  • CVE-2021-4122It was found that a specially crafted LUKS header could trick cryptsetup into disabling encryption during the recovery of the device.
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:cryptsetup2.2.2-r1 · Alpine:v3.11Package registry (OSV)
debian:cryptsetup2:2.3.4-1 · Debian:12Package registry (OSV)
opensuse:cryptsetup2.4.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:cryptsetup0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:cryptsetup-debuginfo0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:cryptsetup-debugsource0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:cryptsetup-devel0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:cryptsetup-libs0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:cryptsetup-libs-debuginfo0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:cryptsetup-reencrypt0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:cryptsetup-reencrypt-debuginfo0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:integritysetup0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:integritysetup-debuginfo0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:veritysetup0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:veritysetup-debuginfo0:2.3.3-2.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records