The default configuration of smbd in Samba before 3.3.11, 3.4.x before 3.4.6, and 3.5.x before 3.5.0rc3, when a writable share exists, allow
Noroxi assessment
Priority: Plan (action score 40/100)
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- Because a ready-made attack tool exists, priority is at least “Plan”.
- Probability of exploitation in the next 30 days: 30.4% (FIRST EPSS); higher than 98.2% of all records.
- Fixed version: samba (Debian:12) 2:3.4.6~dfsg-1; samba (openSUSE:Tumbleweed) 4.5.0-1.1; libsmbclient (Red Hat:enterprise_linux:5::client) 0:3.0.33-3.37.el5.
Add it to your regular patch cycle. Upgrade to samba (Debian:12) 2:3.4.6~dfsg-1; samba (openSUSE:Tumbleweed) 4.5.0-1.1; libsmbclient (Red Hat:enterprise_linux:5::client) 0:3.0.33-3.37.el5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The default configuration of smbd in Samba before 3.3.11, 3.4.x before 3.4.6, and 3.5.x before 3.5.0rc3, when a writable share exists, allows remote authenticated users to leverage a directory traversal vulnerability, and access arbitrary files, by using the symlink command in smbclient to create a symlink containing .. (dot dot) sequences, related to the combination of the unix extensions and wide links options.
- Published
- Mar 10, 2010
- Updated
- Jun 16, 2026
- EPSS
- 30.4% · 98th percentile
- CWE
- CWE-22
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 14 / 40 · 3.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 9 / 30 · 30.4%
- Ready-made attack tool
- 17 / 40 · floor: at least 40
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| samba | samba | cpe:2.3:a:samba:samba |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- samba samba3.3.0
- samba samba3.3.1
- samba samba3.3.10
- samba samba3.3.2
- samba samba3.3.3
- samba samba3.3.4
- samba samba3.3.5
- samba samba3.3.6
- samba samba3.3.7
- samba samba3.3.8
- samba samba3.3.9
- samba samba3.4.0
- samba samba3.4.1
- samba samba3.4.2
- samba samba3.4.3
- samba samba3.4.4
- samba samba3.4.5
- samba samba3.5.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | samba | before 2:3.4.6~dfsg-1 | 2:3.4.6~dfsg-1 |
| openSUSE:Tumbleweed | samba | before 4.5.0-1.1 | 4.5.0-1.1 |
| Red Hat:enterprise_linux:5::client | libsmbclient | before 0:3.0.33-3.37.el5 | 0:3.0.33-3.37.el5 |
| Red Hat:enterprise_linux:5::client | samba-client | before 0:3.0.33-3.37.el5 | 0:3.0.33-3.37.el5 |
| Red Hat:enterprise_linux:5::client | samba-common | before 0:3.0.33-3.37.el5 | 0:3.0.33-3.37.el5 |
| Red Hat:enterprise_linux:5::client | samba-swat | before 0:3.0.33-3.37.el5 | 0:3.0.33-3.37.el5 |
| Red Hat:enterprise_linux:5::client_workstation | libsmbclient-devel | before 0:3.0.33-3.37.el5 | 0:3.0.33-3.37.el5 |
| Red Hat:enterprise_linux:5::client_workstation | samba | before 0:3.0.33-3.37.el5 | 0:3.0.33-3.37.el5 |
| Red Hat:enterprise_linux:5::client_workstation | samba-debuginfo | before 0:3.0.33-3.37.el5 | 0:3.0.33-3.37.el5 |
Same product
samba: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7494Samba since version 3.5.0 and before 4.6.4, 4.5.10 and 4.4.14 is vulnerable to remote code execution vulnerability, allowing a malicious cliKEV99Now
- CVE-2015-0240The Netlogon server implementation in smbd in Samba 3.5.x and 3.6.x before 3.6.25, 4.0.x before 4.0.25, 4.1.x before 4.1.17, and 4.2.x befor66This week
- CVE-2003-0085Buffer overflow in the SMB/CIFS packet fragment re-assembly code for SMB daemon (smbd) in Samba before 2.2.8, and Samba-TNG before 0.3.1, al66This week
Published before and after this one in the same product
- ← EarlierCVE-2010-0787Mar 2, 2010 · client/mount.cifs.c in mount.cifs in smbfs in Samba 3.0.22, 3.0.28a, 3.2.3, 3.3.2, 3.4.0, and 3.4.5 allows local users to mount a CIFS share17Monitor
- ← EarlierCVE-2010-0728Mar 10, 2010 · smbd in Samba 3.3.11, 3.4.6, and 3.5.0, when libcap support is enabled, runs with the CAP_DAC_OVERRIDE capability, which allows remote authe35Monitor
- Later →CVE-2010-1635Jun 17, 2010 · The chain_reply function in process.c in smbd in Samba before 3.4.8 and 3.5.x before 3.5.2 allows remote attackers to cause a denial of serv21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:samba | 2:3.4.6~dfsg-1 · Debian:12 | Package registry (OSV) |
| opensuse:samba | 4.5.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:libsmbclient | 0:3.0.33-3.37.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:libsmbclient-devel | 0:3.0.33-3.37.el5 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:samba | 0:3.0.33-3.37.el5 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:samba-client | 0:3.0.33-3.37.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:samba-common | 0:3.0.33-3.37.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:samba-debuginfo | 0:3.0.33-3.37.el5 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:samba-swat | 0:3.0.33-3.37.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Exploit-DB entry ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | remote | 2010-02-04 |
| Exploit-DB entry | remote | 2010-02-04 |
| Metasploit module | auxiliary/admin/smb/samba_symlink_traversalSamba Symlink Directory Traversalauxiliary | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-35 d
- Published
- TodayOct 20, 2026+6068 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- none
- Availability
- none
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
AV:N/AC:M/Au:S/C:P/I:N/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) { return res.sendStatus(400);}res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- archives.neohapsis.com/archives/fulldisclosure/2010-02/0107.html
- archives.neohapsis.com/archives/fulldisclosure/2010-02/0108.html
- blog.metasploit.com/2010/02/exploiting-samba-symlink-traversal.html
- gitweb.samba.org/?p=samba.git%3Ba=commit%3Bh=bd269443e311d96ef495a9db47d1b95eb83bb8f4
- lists.opensuse.org/opensuse-security-announce/2010-04/msg00001.html
- lists.opensuse.org/opensuse-security-announce/2010-08/msg00001.html
- marc.info/?l=full-disclosure&m=126538598820903&w=2
- marc.info/?l=oss-security&m=126539592603079&w=2
- marc.info/?l=oss-security&m=126540402215620&w=2
- marc.info/?l=oss-security&m=126540733320471&w=2
- marc.info/?l=oss-security&m=126545363428745&w=2
- marc.info/?l=oss-security&m=126777580624790&w=2
- marc.info/?l=samba-technical&m=126539387432412&w=2
- marc.info/?l=samba-technical&m=126540011609753&w=2
- marc.info/?l=samba-technical&m=126540100511357&w=2
- marc.info/?l=samba-technical&m=126540248613395&w=2
- marc.info/?l=samba-technical&m=126540277713815&w=2
- marc.info/?l=samba-technical&m=126540290614053&w=2
- marc.info/?l=samba-technical&m=126540376915283&w=2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.