FedoraOperating system · Fedoraproject
CVE-2022-22995
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 · uneditedThe combination of primitives offered by SMB and AFP in their default configuration allows the arbitrary writing of files. By exploiting these combination of primitives, an attacker can execute arbitrary code.
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 confidenceThis vulnerability involves the interaction between SMB (Server Message Block) and AFP (Apple Filing Protocol) in their default configurations, which together provide primitives allowing arbitrary file writing. An attacker can exploit this file write capability to deploy malicious code and achieve arbitrary code execution on the affected system.
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
= 37= 38= 39< 5.19.117< 5.19.117< 5.19.117< 5.19.117< 5.19.117< 5.19.117< 5.19.117CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify the product typeDetermine if the system is a Fedora Linux host or a Western Digital My Cloud deviceAffected if System is either Fedora 37/38/39 or a WD My Cloud model (Pr2100, Pr4100, Ex4100, Ex2 Ultra, Mirror Gen2, Dl2100, Dl4100)
-
For Fedora: Check if both SMB and AFP are installedRun 'rpm -qa | grep -i samba' to check for Samba packages, and 'rpm -qa | grep -i netatalk' to check for AFP packagesAffected if Both samba and netatalk packages are installed on the system
-
For Fedora: Check if both SMB and AFP services are runningRun 'systemctl status smb' and 'systemctl status netatalk' to check service statusAffected if Both smb and netatalk services are active/running simultaneously
-
For WD My Cloud: Check firmware versionAccess the device dashboard or run 'cat /etc/os-version' or check the web UI under Settings > AboutAffected if Firmware version is lower than 5.19.117 or cannot be determined
-
For WD My Cloud: Check if SMB and AFP are both enabledAccess the device web UI under File Sharing settings and verify if both SMB (Samba) and AFP protocols are turned onAffected if Both SMB and AFP file sharing protocols are enabled on the device
A system is affected if it is a Fedora 37/38/39 with both Samba and Netatalk running, or a WD My Cloud device with firmware below 5.19.117 that has both SMB and AFP protocols enabled simultaneously.
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 · scoped5.19.117
Immediately review and restrict SMB and AFP file sharing configurations, disable unused protocols, implement strict access controls, and consider network segmentation to limit exposure to this critical flaw.
Fedora: Update to latest patched Fedora release; WD My Cloud: Firmware 5.19.117 or later
- For Fedora systems: Run 'dnf update' to receive the latest security patches for the SMB/AFP packages
- For Western Digital My Cloud devices: Navigate to the device settings, check for firmware updates, and update to firmware version 5.19.117 or later
- After updating, verify the SMB and AFP configurations no longer allow arbitrary file writing through symlink manipulation
- Restart the SMB/AFP services if required to apply the security fixes
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
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22995 — 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-22995 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