dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-3592

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-12
Fix available
A fix is available. Upgrade to 4.17.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 symlink following vulnerability was found in Samba, where a user can create a symbolic link that will make 'smbd' escape the configured share path. This flaw allows a remote user with access to the exported part of the file system under a share via SMB1 unix extensions or NFS to create symlinks to files outside the 'smbd' configured share path and gain access to another restricted server's filesystem.

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 symlink following vulnerability in Samba allows a remote authenticated user with access to a share via SMB1 unix extensions or NFS to create symbolic links that escape the configured share path, potentially accessing files outside the intended share boundary.

MitigationUpgrade to a Samba version that addresses this vulnerability, or disable unix extensions and symlink following in shares where not required.

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:= 36= 37
SambaApplication
Affected:>= 4.17.0, < 4.17.2

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 installed Samba version
    Run 'smbstatus --version' or 'rpm -q samba' to determine the Samba version number
    Affected if The version is >= 4.17.0 and < 4.17.2, or on Fedora 36/37 with Samba installed
  2. Verify if SMB1 unix extensions are enabled
    Check smb.conf for 'unix extensions = yes' in the [global] section or per-share configuration, or inspect with 'testparm -v | grep unix extensions'
    Affected if Unix extensions are enabled (set to yes) on any share
  3. Confirm share-level symlink following is permitted
    Review smb.conf for 'follow symlinks = yes' setting in share definitions, or run 'testparm -v' to see all share parameters
    Affected if Follow symlinks is enabled on shares that allow write access
  4. Identify exposed shares accessible via SMB1 or NFS
    List active shares with 'smbstatus -L' or check smb.conf for share definitions accessible to authenticated users
    Affected if Any writable share is accessible via SMB1 with unix extensions or via NFS with the vulnerable configuration present

A user is affected if Samba version is 4.17.0-4.17.2 (or on Fedora 36/37) AND unix extensions are enabled AND symlink following is permitted on accessible shares, allowing escape of share boundaries.

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 4.17.2 or later
Fixed in 4.17.2
Interim mitigation

Upgrade to a Samba version that addresses this vulnerability, or disable unix extensions and symlink following in shares where not required.

Recommended fix High confidence

Samba 4.17.2 or later; Fedora 36 and 37 should update to the patched packages available in their repositories

  1. Check the current Samba version with: smbd --version
  2. For Fedora systems: Run 'sudo dnf update samba' to install the fixed package
  3. For source installations: Download Samba 4.17.2 or later from www.samba.org
  4. Backup the current Samba configuration: cp /etc/samba/smb.conf /etc/samba/smb.conf.bak
  5. Stop the Samba service: sudo systemctl stop smbd nmbd winbindd
  6. Install the updated Samba packages (Fedora) or compile/install from source
  7. Start the Samba service: sudo systemctl start smbd nmbd winbindd
  8. Verify the new version is running: smbd --version
Caveat Samba service restart is required; test configurations before restarting production systems

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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