rsync up to 2.5.7 socket.c open_socket_out RSYNC_PROXY memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in rsync up to 2.5.7. The affected element is the function open_socket_out of the file socket.c. Performing a manipulation of the argument RSYNC_PROXY as part of Environment Variable results in memory corruption.
This vulnerability is known as CVE-2004-2093. Furthermore, an exploit is available.
Details
A vulnerability classified as problematic has been found in rsync up to 2.5.7 (File Transfer Software). This affects the function open_socket_out of the file socket.c. The manipulation of the argument RSYNC_PROXY as part of a Environment Variable leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in the open_socket_out function in socket.c for rsync 2.5.7 and earlier allows local users to cause a denial of service (crash) and possibly execute arbitrary code via a long RSYNC_PROXY environment variable. NOTE: since rsync is not setuid, this issue does not provide any additional privileges beyond those that are already available to the user. Therefore this issue may be REJECTED in the future.
The weakness was published 02/09/2004 (Website). It is possible to read the advisory at archives.neohapsis.com. This vulnerability is uniquely identified as CVE-2004-2093 since 05/19/2005. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (15108), Exploit-DB (152) and OSVDB (45182†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.9
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Timeline
02/09/2004 🔍02/09/2004 🔍
05/19/2005 🔍
05/15/2008 🔍
10/15/2014 🔍
12/11/2024 🔍
Sources
Advisory: archives.neohapsis.comStatus: Not defined
CVE: CVE-2004-2093 (🔍)
GCVE (CVE): GCVE-0-2004-2093
GCVE (VulDB): GCVE-100-21555
X-Force: 15108
OSVDB: 45182 - rsync socket.c open_socket_out Function RSYNC_PROXY Environment Variable Overflow Local DoS
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/15/2014 13:57Updated: 12/11/2024 19:04
Changes: 10/15/2014 13:57 (51), 04/09/2019 10:26 (2), 12/11/2024 19:04 (27)
Complete: 🔍
Cache ID: 216:D38:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.