dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-30788

HIGH · 7.8 CVSS v3.1 Published 2022-05-26
Fix available
A fix is available. Upgrade to after 2021.8.22 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A crafted NTFS image can cause a heap-based buffer overflow in ntfs_mft_rec_alloc in NTFS-3G through 2021.8.22.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A heap-based buffer overflow vulnerability exists in the ntfs_mft_rec_alloc function of NTFS-3G (versions up to 2021.8.22). When mounting a specially crafted malicious NTFS image, the allocator fails to properly validate bounds, leading to heap memory corruption that could enable arbitrary code execution or cause a denial of service.

MitigationUpgrade NTFS-3G to a version beyond 2021.8.22 or apply the vendor-supplied patch; avoid mounting untrusted or unknown NTFS images from external sources until the update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 35= 36
Debian LinuxOperating system
Affected:= 9.0= 10.0= 11.0
Ntfs 3gApplication
Affected:<= 2021.8.22

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check NTFS-3G package version on Debian/Ubuntu
    Run `dpkg -l | grep ntfs-3g` or `apt show ntfs-3g` to retrieve the installed version number
    Affected if The version displayed is 1:2021.8.22 or earlier
  2. Check NTFS-3G package version on Fedora/RHEL
    Run `rpm -qa | grep ntfs-3g` or `dnf list installed ntfs-3g` to retrieve the installed version number
    Affected if The version displayed is 2021.8.22 or earlier
  3. Check NTFS-3G binary version directly
    Run `ntfs-3g --version` to see the version string reported by the binary itself
    Affected if The output shows version 2021.8.22 or any version earlier than 2021.8.22
  4. Identify if NTFS-3G is used for NTFS mount operations
    Check for ntfs-3g in `/sbin/mount.ntfs` or run `mount | grep ntfs` to see active NTFS mounts
    Affected if NTFS-3G is present and used to mount NTFS volumes from external or untrusted sources

A system is affected if NTFS-3G version 2021.8.22 or earlier is installed and used to mount NTFS images, particularly from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2021.8.22
Interim mitigation

Upgrade NTFS-3G to a version beyond 2021.8.22 or apply the vendor-supplied patch; avoid mounting untrusted or unknown NTFS images from external sources until the update is applied.

Recommended fix Moderate confidence

NTFS-3G version newer than 2021.8.22 (e.g., 2022.10.3 or later)

  1. 1. Check the current NTFS-3G version installed: 'ntfs-3g --version' or 'dpkg -l | grep ntfs-3g' (Debian) / 'rpm -qa | grep ntfs-3g' (Fedora)
  2. 2. Update the package repository: 'sudo dnf check-update' (Fedora) or 'sudo apt-get update' (Debian)
  3. 3. Upgrade NTFS-3G to the latest available version: 'sudo dnf upgrade ntfs-3g' (Fedora) or 'sudo apt-get install ntfs-3g' (Debian)
  4. 4. Verify the installed version is newer than 2021.8.22

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30788 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30788 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data