Samba Samba is the standard Windows interoperability suite of programs for Linux and Unix.
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any Samba product.
RSS Feeds for Samba security vulnerabilities
Create a CVE RSS feed including security vulnerabilities found in Samba products with stack.watch. Just hit watch, then grab your custom RSS feed url.
Products by Samba Sorted by Most Security Vulnerabilities since 2018
Known Exploited Samba Vulnerabilities
The following Samba vulnerabilities have been marked by CISA as Known to be Exploited by threat actors.
| Title | Description | Added |
|---|---|---|
| Samba Remote Code Execution Vulnerability |
Samba contains a remote code execution vulnerability, allowing a malicious client to upload a shared library to a writable share and then cause the server to load and execute it. CVE-2017-7494 Exploit Probability: 99.4% |
March 30, 2023 |
The vulnerability CVE-2017-7494: Samba Remote Code Execution Vulnerability is in the top 1% of the currently known exploitable vulnerabilities.
By the Year
In 2026 there have been 40 vulnerabilities in Samba with an average score of 7.6 out of ten. Last year, in 2025 Samba had 8 security vulnerabilities published. That is, 32 more vulnerabilities have already been reported in 2026 as compared to last year. However, the average CVE base score of the vulnerabilities in 2026 is greater by 0.63.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 40 | 7.58 |
| 2025 | 8 | 6.95 |
| 2024 | 1 | 7.50 |
| 2023 | 21 | 6.60 |
| 2022 | 30 | 7.32 |
| 2021 | 6 | 7.13 |
| 2020 | 15 | 6.18 |
| 2019 | 14 | 6.73 |
| 2018 | 20 | 6.71 |
It may take a day or so for new Samba vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Samba Security Vulnerabilities
| CVE | Date | Vulnerability | Products |
|---|---|---|---|
| CVE-2026-70452 | Aug 13, 2026 |
rsync 3.1.0-3.4.x DNS Bypass: Host Blocking Skipped on Lookup Failurersync 3.1.0 before 3.5.0 contains an access control bypass vulnerability that allows remote attackers to circumvent hosts deny rules by inducing DNS resolution failures during hostname-based access control evaluation. When a DNS lookup for a hostname-based deny rule fails, the daemon skips the rule rather than defaulting to a deny decision, enabling attackers who can trigger DNS failures to bypass module-level IP access controls and gain unauthorized access to restricted module file trees. |
|
| CVE-2026-70453 | Aug 13, 2026 |
rsync <3.5.0 DOS via hash_search algorithmic complexityrsync before 3.5.0 contains an algorithmic complexity vulnerability in the hash_search() function that allows a remote attacker to cause a denial of service by delivering a carefully constructed file list. A sender can exploit the quadratic-time worst-case behavior in hash lookups to exhaust receiver CPU resources with a modest number of crafted entries, causing a sustained denial of service. |
|
| CVE-2026-70454 | Aug 13, 2026 |
rsync TLS Cert Validation Fails 3.2.03.2.3, 3.4.4 (OpenSSL/Stunnel)rsync 3.2.0 through 3.2.3 (openssl mode) and rsync-ssl through 3.4.4 (stunnel mode) contain a TLS certificate validation vulnerability that allows on-path attackers to intercept encrypted sessions by presenting self-signed or otherwise invalid certificates. Attackers can exploit the failure to validate server TLS certificates against a trusted CA or verify certificate hostname matching to decrypt or tamper with rsync session content without detection by the client. |
|
| CVE-2026-70455 | Aug 13, 2026 |
rsync 3.4.2<3.5.0 DDoS via --zt Zstd thread abusersync 3.4.2 before 3.5.0 contains a denial of service vulnerability that allows a remote sender to exhaust system resources by specifying the --zt short alias for --compress-threads, which bypasses the refuse options directive's string matching on long option names. Attackers can specify --zt=N with a large value to spawn an unbounded number of Zstandard worker threads on the receiver, exhausting available thread and memory resources. |
|
| CVE-2026-70456 | Aug 13, 2026 |
rsync OOB Write in read_args() 3.0.1<3.5.0rsync 3.0.1 before 3.5.0 contains an out-of-bounds write vulnerability in the read_args() function that allows a malicious sender to corrupt adjacent heap memory by sending a crafted argument list. When the argument count causes the argv allocation to be exactly full, the trailing NULL terminator is written one slot beyond the allocation boundary, corrupting adjacent heap memory. |
|
| CVE-2026-70457 | Aug 13, 2026 |
rsync 3.x OOB write in parse_size_arg before 3.5.0rsync 3.2.3 before 3.5.0 contains an out-of-bounds write in parse_size_arg() where the return value of snprintf() is used directly as an index into a .bss-segment array without bounds checking. When snprintf truncates the formatted size string, the return value equals the number of characters that would have been written including the truncated portion, and this value may exceed the array length. The subsequent indexed write targets memory outside the intended array bounds, corrupting .bss memory. |
|
| CVE-2026-70458 | Aug 13, 2026 |
rsync <3.5.0: OOB Write via HLINK_BUMP (missing F_SUM)rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data. |
|
| CVE-2026-70459 | Aug 13, 2026 |
rsync <3.5.0 Null Pointer Deref in child daemon via dot entryrsync 3.0.0 before 3.5.0 contains a null pointer dereference vulnerability in the daemon child process that allows remote attackers to crash the daemon by sending a file list whose first entry is a dot entry not typed as a directory. The daemon dereferences the first file list entry as a directory structure pointer without verifying the entry type, resulting in an invalid or uninitialized pointer dereference that terminates the client connection. |
|
| CVE-2026-70460 | Aug 13, 2026 |
rsync 2.3.3-3.5.0 Path Traversal via --partial-dir/--backup-dir symlinksrsync 2.3.3 before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to escape the module root by exploiting symlinks within the module file tree when using --partial-dir or --backup-dir options. Attackers with write access to place a symlink under the module root, or who can exploit a pre-existing trusted symlink, can direct file writes to locations outside the intended module root, achieving arbitrary file write relative to the module root parent. |
|
| CVE-2026-70461 | Aug 13, 2026 |
Rsync 3.2.53.4.9: Heap OOB Write via files-fromrsync 3.2.5 before 3.5.0 contains a heap out-of-bounds write vulnerability that allows remote unauthenticated attackers to write one attacker-controlled byte past the end of a heap allocation by supplying a crafted files-from entry. Attackers can trigger the vulnerability against a read-only rsync daemon module by providing a files-from entry containing both an interior and trailing backslash, causing the add_implied_include() function to under-count the trailing backslash when sizing the destination buffer. |
|
| CVE-2026-70462 | Aug 13, 2026 |
Signed Int Overflow in rsync 3.1.0-<3.5.0 I/O Timeout Resource Exhaustionrsync 3.1.0 before 3.5.0 contains a signed integer overflow vulnerability in the I/O timeout implementation that allows attackers to permanently disable connection timeouts by injecting MSG_IO_TIMEOUT messages carrying non-positive (zero or negative) values. Attackers can craft malicious MSG_IO_TIMEOUT messages that cause the timeout variable to wrap to a non-positive value, preventing the timeout check from firing and enabling idle or stalled connections to hold daemon slots indefinitely, leading to resource exhaustion. |
|
| CVE-2026-70463 | Aug 13, 2026 |
rsync 3.1.0-3.4.x Auth Users Bypass via @Group Name Parsingrsync 3.1.0 before 3.5.0 contains an authorization bypass in auth users directive parsing. The auth users parser uses comma-only tokenization when splitting the user list, which fails to correctly handle entries of the form @Group Name where the group name contains a space. The space within the group name causes the parser to split the entry at the space boundary, discarding the deny rule associated with the group. An authenticated user whose username or group membership would be denied by an @Group Name auth users entry can connect to a restricted module because the deny rule is silently discarded during parsing. |
|
| CVE-2026-70464 | Aug 13, 2026 |
DoS via connection slot exhaustion in rsync 2.0.03.5.0rsync daemon 2.0.0 before 3.5.0 contains a denial of service vulnerability that allows unauthenticated remote attackers to exhaust daemon connection slots by stalling the handshake process before or after module selection without triggering the I/O timeout. Attackers can open many simultaneous connections and trickle data at the minimum rate to avoid timeout, or stall entirely before module selection where no timeout applies, consuming all available connection slots and denying service to legitimate clients. |
|
| CVE-2026-53801 | Aug 13, 2026 |
rsync <3.5.0 Symlink Race in Sender Directory Scanningrsync before 3.5.0 contains a symlink race condition vulnerability in the sender's directory scanning logic that allows attackers to cause the sender to enumerate and transfer files outside the module root's intended subtree. Attackers who can create or manipulate symlinks in a path component of the scanned tree can replace a symlink with a directory entry pointing outside the module root between the lstat() call and the subsequent opendir() call, exposing files beyond the intended root in both daemon-mode and non-daemon sender-side scanning. |
|
| CVE-2026-53800 | Aug 13, 2026 |
rsync <=3.5.0 symlink race in --remove-source-files cause arbitrary file deletionrsync before 3.5.0 contains a symlink race condition vulnerability in the --remove-source-files feature that allows attackers with symlink creation access to cause arbitrary file deletion. Attackers can atomically substitute a symlink for a source file between transfer completion and the unlink() call, causing rsync to delete the symlink target rather than the intended source file. |
|
| CVE-2026-53799 | Aug 13, 2026 |
Rsync <3.5.0 Symlink Race Condition Enables Local Privilege Escalationrsync before 3.5.0 contains a symlink race condition vulnerability that allows local attackers to cause rsync to apply arbitrary ACLs or extended attributes to unintended files by substituting a symlink at a predictable destination path between the file write and the subsequent acl_set_file() or lsetxattr() call. Attackers can exploit this timing window to redirect ACL and xattr application through a crafted symlink to files outside the intended destination tree, potentially granting elevated permissions and enabling local privilege escalation. |
|
| CVE-2026-53797 | Aug 13, 2026 |
rsync <3.5.0 Symlink Race: File Disclosure via Parent Directory Manipulationrsync before 3.5.0 contains a symlink race condition vulnerability in the sender's source tree traversal that allows an attacker who can manipulate a parent directory of the source tree to redirect file reads to unintended paths. Attackers can atomically replace a parent directory component with a symlink pointing outside the source root between path resolution and file open operations to disclose file contents outside the intended transfer root. |
|
| CVE-2026-53796 | Aug 13, 2026 |
rsync<3.5.0 TOCTOU in nondaemon receiver destdir handlingrsync before 3.5.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the non-daemon receiver's destination directory handling that allows an attacker who can manipulate destination path parent components to redirect file writes to unintended locations. Attackers can substitute a symlink for a component of the destination path between the path resolution and chdir() call, causing the receiver's working directory to be established outside the intended destination tree so that subsequent relative-path file writes land in unintended filesystem locations. |
|
| CVE-2026-53795 | Aug 13, 2026 |
rsync <3.5.0 Arbitrary File Write via --temp-dir / --link-dest (Rename Bypass)rsync before 3.5.0 contains an arbitrary file write vulnerability that allows attackers to write files outside the intended destination tree by specifying an absolute path via --temp-dir or --link-dest options. The rename-confinement logic is bypassed when these options resolve to paths outside the destination tree, enabling attacker-controlled values to write files to arbitrary locations accessible to the rsync process. |
|
| CVE-2026-53794 | Aug 13, 2026 |
rsync <3.5.0 --max-alloc Logic Error Enables Unlimited Allocation & DoSrsync before 3.5.0 contains a logic error in --max-alloc handling that allows a sender or configuration setting --max-alloc=0 to disable allocation sanity checks entirely rather than enforcing a zero-byte cap. Attackers can exploit this flaw to cause the receiver to attempt unbounded memory allocations for file list and data structures, potentially exhausting available memory and causing a denial of service. |
|
| CVE-2026-53793 | Aug 13, 2026 |
rsync <3.5.0 Path Confinement Bypass via /./ Module Root Markerrsync before 3.5.0 contains a path confinement bypass vulnerability that allows remote clients to escape the intended inner-module root confinement by constructing paths that resolve outside the chroot boundary when the module root contains a /./ boundary marker. Attackers can exploit improper handling of the /./ notation or forge delta-basis transfers referencing xname paths that cross the /./ boundary to gain unauthorized read or write access to files outside the module's subtree. |
|
| CVE-2026-53792 | Aug 13, 2026 |
Rsync <3.5.0 OOB Read via Zero-Checksum Blockrsync before 3.5.0 contains an out-of-bounds read vulnerability in the sender-side block matching logic that allows a malicious receiver to trigger memory access before the start of an allocated buffer by sending a crafted checksum block with a length of zero. Attackers can send a specially crafted checksum set containing a zero-length block to cause a negative offset calculation during delta computation, resulting in an out-of-bounds read of file data buffer memory on the sender side. |
|
| CVE-2026-53791 | Aug 13, 2026 |
IP Spoofing via PROXY header in rsync daemon <3.5.0rsync daemon before 3.5.0 contains an IP address spoofing vulnerability that allows unauthenticated remote attackers to bypass IP-based access controls by sending a crafted PROXY protocol header with a forged source address. Attackers who can connect directly to the rsync daemon can inject a spoofed source IP in the PROXY protocol header to circumvent hosts allow/deny rules, gaining unauthorized access that would otherwise be blocked based on their real source address. |
|
| CVE-2026-53790 | Aug 13, 2026 |
rsync <3.5.0 Command & Argument Injection via ENV & Hooksrsync before 3.5.0 contains multiple command and argument injection vulnerabilities that allow attackers to execute arbitrary commands by supplying malicious input through several code paths, including the RSYNC_CONNECT_PROG environment variable, daemon hooks, the rsync-ssl wrapper, and remote-shell command newline injection. Attackers can inject shell metacharacters or newline characters into unsanitized user-supplied values such as hostnames and hostspecs to execute arbitrary commands under the privileges of the rsync process or the invoking user. |
|
| CVE-2026-53789 | Aug 13, 2026 |
rsync 3.5.0 Improper Path Handling in --delete (CVE-2026-53789)rsync before 3.5.0 contains an improper path handling vulnerability that allows a malicious sender to expand the scope of --delete operations beyond the intended destination subtree by sending a crafted file list that causes rsync to reclassify implied parent directory entries or treat synthetic paths as the transfer root. Attackers can exploit multiple variants including implied parent reclassification, synthetic root path construction, legacy protocol behavior below version 30, and non-directory root handling to cause the receiver to delete files outside the authorized destination directory. |
|
| CVE-2026-53788 | Aug 13, 2026 |
rsync <=3.5.0 Newline Injection in Name-Converter UID/GID Mappingrsync before 3.5.0 contains a newline injection vulnerability in the name-converter uid/gid mapping interface that allows local attackers to forge protocol messages by creating user or group names containing newline characters. Attackers can inject malicious newline characters into names communicated over the pipe-based line-oriented protocol to cause the rsync daemon to process attacker-influenced data as legitimate protocol input, corrupting uid/gid mapping logic. |
|
| CVE-2026-53798 | Aug 13, 2026 |
Rsync pre-3.5.0 Priv Conf in name-conv uid/gid mapping root file ownershiprsync before 3.5.0 contains a privilege confusion vulnerability in the name-converter subprocess uid/gid mapping that allows local attackers to cause transferred files to be owned by root by influencing name-converter responses to return empty values. When the name-converter subprocess returns an empty response for a uid or gid lookup, rsync incorrectly interprets it as a successful resolution to uid/gid 0 (root) rather than a lookup failure, and if the name-converter also signals fake super-user status, rsync proceeds with root ownership assignments for transferred files. |
|
| CVE-2026-53786 | Aug 13, 2026 |
rsync <3.5.0 Filter Bypass via --filter Merge File Directivesrsync before 3.5.0 contains a filter rule bypass vulnerability that allows authenticated clients to override module-level filter restrictions by supplying malicious --filter merge file directives. Attackers can inject client-side merge file directives during filter evaluation to introduce rules that supersede daemon module-level restrictions, gaining access to files the module filter was intended to exclude. |
|
| CVE-2026-53785 | Aug 13, 2026 |
Rsync 3.5.0 Path Traversal via Symlink in --relative Modersync before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to write files outside the intended destination directory tree by crafting relative paths with symlink components in --relative mode. The make_path() function follows symlinks pointing outside the destination tree while creating intermediate directories without verifying that created paths remain within the destination boundary, enabling arbitrary file writes on the receiver's filesystem. |
|
| CVE-2026-53784 | Aug 13, 2026 |
RSync Path Traversal via Symlinked Module Root (<3.5.0)rsync before 3.5.0 contains a path traversal vulnerability that allows remote clients to access files outside the intended module root when use chroot is disabled and the module root path or a component of it is a symlink. The daemon calls chdir() to the module root at session initialization without resolving symlinks via realpath() or equivalent, causing subsequent relative-path operations to reference files relative to the symlink target rather than the intended module root, enabling unauthorized file access. |
|
| CVE-2026-53783 | Aug 13, 2026 |
rsync 3.5.0 rrsync TOCTOU: symlink escape & unsafe flag abusersync before 3.5.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the rrsync restricted shell wrapper that allows authenticated clients to escape enforced directory restrictions by substituting a symlink for a path component after validation but before transfer processing. Attackers can additionally leverage unrestricted flags such as --copy-unsafe-links, -D, and --log-file through rrsync to read or write files outside the permitted directory subtree. |
|
| CVE-2026-53803 | Aug 13, 2026 |
rsync <3.5.0 Symlink Following Allows Local Privilege Escalationrsync before 3.5.0 contains a symlink following vulnerability that allows local attackers to overwrite arbitrary files by placing a symlink at a predictable output path such as --log-file, --write-batch, or daemon-mode log and statistics paths. Attackers can exploit rsync's failure to reject symlinks during ancillary file writes to redirect output to arbitrary filesystem locations, achieving local privilege escalation on installations where rsync runs with elevated privileges such as setuid or privileged daemon configurations. |
|
| CVE-2026-53802 | Aug 13, 2026 |
Arbitrary File Read in rsync <3.5.0 via symlink handlingrsync before 3.5.0 contains an arbitrary file read vulnerability that allows attackers to read files accessible to the rsync daemon process by exploiting symlink following in input configuration file handling including --files-from, --password-file, and filter merge files. Attackers can place a symlink at a predictable --files-from or --password-file path, or supply a --files-from path that escapes the daemon module root, to read arbitrary files accessible to the rsync process. |
|
| CVE-2026-29518 | May 20, 2026 |
Rsync <=3.4.3 TOCTOU Race Allows Arbitrary File Write/Privilege EscalationRsync versions before 3.4.3 contain a time-of-check to time-of-use (TOCTOU) race condition in daemon file handling that allows attackers to redirect file writes outside intended directories by replacing parent directory components with symbolic links. Attackers with write access to a module path can exploit this race condition to create or overwrite arbitrary files, potentially modifying sensitive system files and achieving privilege escalation when the daemon runs with elevated privileges. This vulnerability can only be triggered if the chroot setting is false. |
|
| CVE-2026-43617 | May 20, 2026 |
Rsync Hostname-based ACL bypass <3.4.3: Auth bypass via PTRRsync version 3.4.2 and prior contain an authorization bypass vulnerability in the rsync daemon's hostname-based access control list enforcement when configured with chroot. Attackers can bypass hostname-based deny rules by controlling the PTR record for their source IP address, allowing connections from hostnames that administrators intended to deny when reverse DNS resolution fails and defaults to UNKNOWN. |
|
| CVE-2026-43618 | May 20, 2026 |
Rsync 3.4.2 and earlier Integer Overflow in compressed-token decoderRsync version 3.4.2 and prior contain an integer overflow vulnerability in the compressed-token decoder where a 32-bit signed counter is not checked for overflow, allowing a malicious sender to trigger an overflow that causes the receiver process to read and return data from outside the intended buffer bounds. Attackers can exploit this vulnerability to disclose process memory contents including environment variables, passwords, heap and stack data, and library memory pointers, significantly reducing ASLR effectiveness and facilitating further exploitation. |
|
| CVE-2026-43619 | May 20, 2026 |
rsync 3.4.2 and earlier Symlink Race Condition in Path-based SyscallsRsync version 3.4.2 and prior contain symlink race condition vulnerabilities in path-based system calls including chmod, lchown, utimes, rename, unlink, mkdir, symlink, mknod, link, rmdir, and lstat that allow local attackers to redirect operations to files outside the exported rsync module. Attackers with local filesystem access can exploit the timing window between path resolution and syscall execution by swapping symlinks to apply sender-supplied permissions, ownership, timestamps, or filenames to arbitrary files outside the intended module boundary on rsync daemons configured with 'use chroot = no'. |
|
| CVE-2026-43620 | May 20, 2026 |
Rsync <3.4.3: Receiver-side OOB array read crash via CF_INC_RECURSERsync version 3.4.2 and prior contain a receiver-side out-of-bounds array read vulnerability in recv_files() in receiver.c that allows a malicious rsync server to crash the rsync client process. Attackers can exploit the vulnerability by setting CF_INC_RECURSE in compatibility flags and sending a specially crafted file list where the first sorted entry is not the leading dot directory, followed by a transfer record with ndx=0 and an iflag word without ITEM_TRANSFER, causing the receiver to read 8 bytes before the allocated pointer array and dereference an invalid pointer at an unmapped address, resulting in a deterministic SIGSEGV crash of the rsync client. |
|
| CVE-2026-45232 | May 20, 2026 |
Rsync <3.4.3: OOB stack write in establish_proxy_connection()Rsync versions before 3.4.3 contain an off-by-one out-of-bounds stack write vulnerability in the establish_proxy_connection() function in socket.c that allows network attackers to corrupt stack memory by sending a malformed HTTP proxy response. Attackers can exploit this by positioning themselves between the client and proxy or controlling the proxy server to send a response line of 1023 or more bytes without a newline terminator, causing a null byte to be written to an out-of-bounds stack address when the RSYNC_PROXY environment variable is set. |
|
| CVE-2026-41035 | Apr 16, 2026 |
rsync 3.0.13.4.1 Receiver UAF in receive_xattr (qsort untrusted len)In rsync 3.0.1 through 3.4.1, receive_xattr relies on an untrusted length value during a qsort call, leading to a receiver use-after-free. The victim must run rsync with -X (aka --xattrs). On Linux, many (but not all) common configurations are vulnerable. Non-Linux platforms are more widely vulnerable. |
|
| CVE-2025-10230 | Nov 07, 2025 |
Samba WINS Hook RCE via Unvalidated NetBIOS NamesA flaw was found in Samba, in the front-end WINS hook handling: NetBIOS names from registration packets are passed to a shell without proper validation or escaping. Unsanitized NetBIOS name data from WINS registration packets are inserted into a shell command and executed by the Samba Active Directory Domain Controllers wins hook, allowing an unauthenticated network attacker to achieve remote command execution as the Samba process. |
|
| CVE-2025-9640 | Oct 15, 2025 |
Samba vfs_streams_xattr Heap LE Leading to ID DisclosureA flaw was found in Samba, in the vfs_streams_xattr module, where uninitialized heap memory could be written into alternate data streams. This allows an authenticated user to read residual memory content that may include sensitive data, resulting in an information disclosure vulnerability. |
|
| CVE-2025-0620 | Jun 06, 2025 |
Samba smbd Group Membership Flaw Exposes SharesA flaw was found in Samba. The smbd service daemon does not pick up group membership changes when re-authenticating an expired SMB session. This issue can expose file shares until clients disconnect and then connect again. |
|
| CVE-2024-12084 | Jan 15, 2025 |
rsync Daemon Heap Bof via Checksum Length OverrunA heap-based buffer overflow flaw was found in the rsync daemon. This issue is due to improper handling of attacker-controlled checksum lengths (s2length) in the code. When MAX_DIGEST_LEN exceeds the fixed SUM_LENGTH (16 bytes), an attacker can write out of bounds in the sum2 buffer. |
|
| CVE-2024-12086 | Jan 14, 2025 |
Rsync Server Remote File Enumeration via Checksum ExploitA flaw was found in rsync. It could allow a server to enumerate the contents of an arbitrary file from the client's machine. This issue occurs when files are being copied from a client to a server. During this process, the rsync server will send checksums of local data to the client to compare with in order to determine what data needs to be sent to the server. By sending specially constructed checksum values for arbitrary files, an attacker may be able to reconstruct the data of those files byte-by-byte based on the responses from the client. |
|
| CVE-2024-12087 | Jan 14, 2025 |
Path traversal in rsync via --inc-recursive optionA path traversal vulnerability exists in rsync. It stems from behavior enabled by the `--inc-recursive` option, a default-enabled option for many client options and can be enabled by the server even if not explicitly enabled by the client. When using the `--inc-recursive` option, a lack of proper symlink verification coupled with deduplication checks occurring on a per-file-list basis could allow a server to write files outside of the client's intended destination directory. A malicious server could write malicious files to arbitrary locations named after valid directories/paths on the client. |
|
| CVE-2024-12085 | Jan 14, 2025 |
Rsync: Checksum Length Manipulation Enables Stack Data LeakA flaw was found in rsync which could be triggered when rsync compares file checksums. This flaw allows an attacker to manipulate the checksum length (s2length) to cause a comparison between a checksum and uninitialized memory and leak one byte of uninitialized stack data at a time. |
|
| CVE-2024-12088 | Jan 14, 2025 |
Rsync --safe-links Path Traversal, Arbitrary File WriteA flaw was found in rsync. When using the `--safe-links` option, the rsync client fails to properly verify if a symbolic link destination sent from the server contains another symbolic link within it. This results in a path traversal vulnerability, which may lead to arbitrary file write outside the desired directory. |
|
| CVE-2020-25720 | Nov 17, 2024 |
Samba Active Directory Object Creation Privilege Escalation VulnerabilityA vulnerability was found in Samba where a delegated administrator with permission to create objects in Active Directory can write to all attributes of the newly created object, including security-sensitive attributes, even after the object's creation. This issue occurs because the administrator owns the object due to the lack of an Access Control List (ACL) at the time of creation and later being recognized as the 'creator owner.' The retained significant rights of the delegated administrator may not be well understood, potentially leading to unintended privilege escalation or security risks. |
|
| CVE-2023-46768 | Nov 08, 2023 |
Samba idmap Multi-threading Race Causing Feature AbuseMulti-thread vulnerability in the idmap module. Successful exploitation of this vulnerability may cause features to perform abnormally. |
|