FedoraOperating system · Fedoraproject
CVE-2022-30785
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 · uneditedA file handle created in fuse_lib_opendir, and later used in fuse_lib_readdir, enables arbitrary memory read and write operations in NTFS-3G through 2021.8.22 when using libfuse-lite.
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 confidenceA file handle created in fuse_lib_opendir and subsequently used in fuse_lib_readdir in NTFS-3G versions through 2021.8.22 contains a memory management flaw when using libfuse-lite, allowing arbitrary memory read and write operations. This stems from improper handle lifecycle management between the directory open and read operations.
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
= 35= 36
Debian LinuxOperating system
= 9.0= 10.0= 11.0<= 2021.8.22CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify NTFS-3G installation and versionRun 'ntfs-3g --version' or check your system's package manager for the installed ntfs-3g package versionAffected if The installed version is 2021.8.22 or earlier
-
Confirm libfuse-lite is in useCheck which libfuse library ntfs-3g is linked against by running 'ldd $(which ntfs-3g)' or inspecting the compile-time configuration. Look for libfuse-lite specifically rather than standard libfuse.Affected if NTFS-3G is linked against libfuse-lite instead of the standard libfuse library
-
Check for active NTFS mountsRun 'mount -t ntfs-3g' or 'mount | grep ntfs' to see if NTFS-3G is currently mounting any NTFS filesystemsAffected if NTFS-3G with the vulnerable libfuse-lite configuration is actively mounting NTFS partitions
You are affected if NTFS-3G version 2021.8.22 or earlier is installed AND it is using libfuse-lite rather than standard libfuse, with active NTFS mounts in place.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade NTFS-3G to version 2021.8.22 or later, or ensure libfuse-lite is not used in favor of the standard libfuse implementation.
NTFS-3G version newer than 2021.8.22 (e.g., 2022.10.3 or later stable release)
- 1. Check current NTFS-3G version: ntfs-3g --version
- 2. For Debian systems: Run 'apt update && apt install ntfs-3g' to upgrade to the latest available version in the repository
- 3. For Fedora systems: Run 'dnf update ntfs-3g' to upgrade to the latest available version
- 4. Verify the new version is greater than 2021.8.22
- 5. If using libfuse-lite, consider rebuilding NTFS-3G with standard libfuse instead as an additional precaution
- 6. Remount any NTFS filesystems to ensure the new version is actively used
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30785 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-30785 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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