A malicious client acting as the receiver of an rsync file transfer can trigger an out of bounds read of a heap based buffer, via a negativ…
A malicious client acting as the receiver of an rsync file transfer can trigger an out of bounds read of a heap based buffer, via a negative array index. The malicious rsync client requires at least read access to the remote rsync module in order to trigger the issue.
The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.
https://cwe.mitre.org/data/definitions/129.html →Open in CWE collection →Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice.
https://capec.mitre.org/data/definitions/100.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| rsync | Tracked | |
| rsync | Tracked | |
| rsync | Tracked | |
| rsync | Tracked | |
| rsync | Tracked | |
| rsync | Tracked | |
| rsync | Tracked | |
| rsync | Tracked | |
| rsync-server | Tracked |