CVE-2004-0815
published 2004-11-03CVE-2004-0815: The unix_clean_name function in Samba 2.2.x through 2.2.11, and 3.0.x before 3.0.2a, trims certain directory names down to absolute paths, which could allow…
PriorityP335high7.5CVSS 2.0
AVNACLAuNCPIPAP
EPSS
4.89%
91.2th percentile
The unix_clean_name function in Samba 2.2.x through 2.2.11, and 3.0.x before 3.0.2a, trims certain directory names down to absolute paths, which could allow remote attackers to bypass the specified share restrictions and read, write, or list arbitrary files via "/.////" style sequences in pathnames.
Affected
25 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | samba | < samba 3.0.6-1 (bookworm) | samba 3.0.6-1 (bookworm) |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | — | — |
| samba | samba | >= 0 < 3.0.6-1 | 3.0.6-1 |
| samba | samba | >= 0 < 3.0.6-1 | 3.0.6-1 |
| samba | samba | >= 0 < 3.0.6-1 | 3.0.6-1 |
| samba | samba | >= 0 < 3.0.6-1 | 3.0.6-1 |
CVSS provenance
nvdv2.07.5HIGHAV:N/AC:L/Au:N/C:P/I:P/A:P
osv7.5HIGH
vendor_debian7.5HIGH
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-fmc4-f425-jjcv: The unix_clean_name function in Samba 2
ghsa_unreviewed·2022-04-29
CVE-2004-0815 [HIGH] GHSA-fmc4-f425-jjcv: The unix_clean_name function in Samba 2
The unix_clean_name function in Samba 2.2.x through 2.2.11, and 3.0.x before 3.0.2a, trims certain directory names down to absolute paths, which could allow remote attackers to bypass the specified share restrictions and read, write, or list arbitrary files via "/.////" style sequences in pathnames.
OSV
CVE-2004-0815: The unix_clean_name function in Samba 2
osv·2004-11-03·CVSS 7.5
CVE-2004-0815 [HIGH] CVE-2004-0815: The unix_clean_name function in Samba 2
The unix_clean_name function in Samba 2.2.x through 2.2.11, and 3.0.x before 3.0.2a, trims certain directory names down to absolute paths, which could allow remote attackers to bypass the specified share restrictions and read, write, or list arbitrary files via "/.////" style sequences in pathnames.
Red Hat
security flaw
vendor_redhat·2004-09-30·CVSS 7.5
CVE-2004-0815 [HIGH] security flaw
security flaw
The unix_clean_name function in Samba 2.2.x through 2.2.11, and 3.0.x before 3.0.2a, trims certain directory names down to absolute paths, which could allow remote attackers to bypass the specified share restrictions and read, write, or list arbitrary files via "/.////" style sequences in pathnames.
Debian
CVE-2004-0815: samba - The unix_clean_name function in Samba 2.2.x through 2.2.11, and 3.0.x before 3.0...
vendor_debian·2004·CVSS 7.5
CVE-2004-0815 [HIGH] CVE-2004-0815: samba - The unix_clean_name function in Samba 2.2.x through 2.2.11, and 3.0.x before 3.0...
The unix_clean_name function in Samba 2.2.x through 2.2.11, and 3.0.x before 3.0.2a, trims certain directory names down to absolute paths, which could allow remote attackers to bypass the specified share restrictions and read, write, or list arbitrary files via "/.////" style sequences in pathnames.
Scope: local
bookworm: resolved (fixed in 3.0.6-1)
bullseye: resolved (fixed in 3.0.6-1)
forky: resolved (fixed in 3.0.6-1)
sid: resolved (fixed in 3.0.6-1)
trixie: resolved (fixed in 3.0.6-1)
No detection rules found.
No public exploits indexed.
CWE
Path Equivalence: '/./' (Single Dot Directory)
mitre_cwe·CVSS 5.0
[MEDIUM] CWE-55 Path Equivalence: '/./' (Single Dot Directory)
CWE-55: Path Equivalence: '/./' (Single Dot Directory)
The product accepts path input in the form of single dot directory exploit ('/./') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Confidentiality, Integrity. Impact: Read Files or Directories, Modify Files or Directories.
Potential Mitigations:
[Implementation] Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by
CWE
Improper Resolution of Path Equivalence
mitre_cwe
CWE-41 Improper Resolution of Path Equivalence
CWE-41: Improper Resolution of Path Equivalence
The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object.
Path equivalence is usually employed in order to circumvent access controls expressed using an incomplete set of file name or file path representations. This is different from path traversal, wherein the manipulations are performed to generate a name for a different object.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Confidentiality, Integrity, Access Control. Impact: Read Files or Directories, Modify Files or Directories, Bypass Protection Mechanism. A
CWE
Collapse of Data into Unsafe Value
mitre_cwe
CWE-182 Collapse of Data into Unsafe Value
CWE-182: Collapse of Data into Unsafe Value
The product filters data in a way that causes it to be reduced or "collapsed" into an unsafe value that violates an expected security property.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Access Control. Impact: Bypass Protection Mechanism.
Detection Methods:
Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts
http://distro.conectiva.com.br/atualizacoes/?id=a&anuncio=000873http://marc.info/?l=bugtraq&m=109655827913457&w=2http://sunsolve.sun.com/search/document.do?assetkey=1-26-101584-1http://sunsolve.sun.com/search/document.do?assetkey=1-26-57664-1http://sunsolve.sun.com/search/document.do?assetkey=1-66-200529-1http://us4.samba.org/samba/news/#security_2.2.12http://www.debian.org/security/2004/dsa-600http://www.idefense.com/application/poi/display?id=146&type=vulnerabilities&flashstatus=truehttp://www.mandrakesecure.net/en/advisories/advisory.php?name=MDKSA-2004:104http://www.novell.com/linux/security/advisories/2004_35_samba.htmlhttp://www.redhat.com/support/errata/RHSA-2004-498.htmlhttp://www.securityfocus.com/archive/1/377618http://www.securityfocus.com/bid/11281http://www.trustix.org/errata/2004/0051/https://bugzilla.fedora.us/show_bug.cgi?id=2102https://exchange.xforce.ibmcloud.com/vulnerabilities/17556http://distro.conectiva.com.br/atualizacoes/?id=a&anuncio=000873http://marc.info/?l=bugtraq&m=109655827913457&w=2http://sunsolve.sun.com/search/document.do?assetkey=1-26-101584-1http://sunsolve.sun.com/search/document.do?assetkey=1-26-57664-1http://sunsolve.sun.com/search/document.do?assetkey=1-66-200529-1http://us4.samba.org/samba/news/#security_2.2.12http://www.debian.org/security/2004/dsa-600http://www.idefense.com/application/poi/display?id=146&type=vulnerabilities&flashstatus=truehttp://www.mandrakesecure.net/en/advisories/advisory.php?name=MDKSA-2004:104http://www.novell.com/linux/security/advisories/2004_35_samba.htmlhttp://www.redhat.com/support/errata/RHSA-2004-498.htmlhttp://www.securityfocus.com/archive/1/377618http://www.securityfocus.com/bid/11281http://www.trustix.org/errata/2004/0051/https://bugzilla.fedora.us/show_bug.cgi?id=2102https://exchange.xforce.ibmcloud.com/vulnerabilities/17556
2004-11-03
Published