dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-30786

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_names_full_collate 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_names_full_collate function of NTFS-3G (versions through 2021.8.22). The flaw is triggered when parsing a specially crafted NTFS image, allowing potential code execution or denial of service via heap memory corruption.

MitigationUpdate NTFS-3G to a version beyond 2021.8.22 that contains the fix for this vulnerability. Alternatively, implement input validation and bounds checking in the ntfs_names_full_collate function if using a maintained fork.

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 if NTFS-3G is installed
    Run 'ntfs-3g --version' or check your package manager (e.g., 'rpm -q ntfs-3g' on Fedora, 'dpkg -l ntfs-3g' on Debian)
    Affected if NTFS-3G is installed and the version is 2021.8.22 or earlier
  2. Verify the exact NTFS-3G version
    Run 'ntfs-3g --version' to get the precise version number, or inspect the package version via your distribution's package manager
    Affected if The version is 2021.8.22 or any earlier version (the vulnerability affects versions through 2021.8.22)
  3. Confirm the vulnerable library is present
    Check for the presence of libntfs-3g (e.g., 'ldconfig -p | grep ntfs' or locate the shared library file)
    Affected if libntfs-3g is present on the system, indicating the vulnerable code is available to be called
  4. Determine if NTFS mounting is in use
    Check for active NTFS mounts (run 'mount | grep ntfs' or review /etc/mtab), or check for scripts/binaries that mount NTFS images
    Affected if NTFS filesystems are being mounted or NTFS images are being parsed, enabling the vulnerable ntfs_names_full_collate function to be triggered

You are affected if NTFS-3G version 2021.8.22 or earlier is installed and NTFS image parsing/mounting functionality is in use on your system.

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

Update NTFS-3G to a version beyond 2021.8.22 that contains the fix for this vulnerability. Alternatively, implement input validation and bounds checking in the ntfs_names_full_collate function if using a maintained fork.

Recommended fix High confidence

NTFS-3G version 2022.10.3 or later (which contains the fix for the heap-based buffer overflow in ntfs_names_full_collate)

  1. Check current NTFS-3G version: rpm -q ntfs-3g (Fedora) or dpkg -l ntfs-3g (Debian)
  2. For Fedora: Run 'dnf update ntfs-3g' or 'dnf upgrade ntfs-3g' to install the latest security update
  3. For Debian: Run 'apt-get update && apt-get install --only-upgrade ntfs-3g' to apply the security patch
  4. Verify the installed version is 2022.10.3 or later using: rpm -q ntfs-3g or dpkg -l ntfs-3g
Caveat Minimal risk - NTFS-3G is a stable utility and this is a security patch; however, always test mounting NTFS images in a non-production environment first

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

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30786 — 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-30786 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