# CVE-2018-5764: Security feature bypass in n/a

> Remote attackers can bypass argument sanitization in rsyncd by using multiple --protect-args flags, potentially exposing sensitive data or enabling further attacks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-5764, DEBIAN-CVE-2018-5764, DLA-1247-1, DLA-2833-1, GHSA-qp2v-jrh4-vgj2, MGASA-2018-0103, SUSE-SU-2018:0172-1, SUSE-SU-2018:0174-1, UBUNTU-CVE-2018-5764

## What is CVE-2018-5764?

CVE-2018-5764 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 17 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The parse_arguments function in options.c in rsyncd in rsync before 3.1.3 does not prevent multiple --protect-args uses, which allows remote attackers to bypass an argument-sanitization protection mechanism.

## Which versions are affected by CVE-2018-5764?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rsync` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 3.1.0-13.10.1 |
| `rsync` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 3.1.0-13.10.1 |
| `rsync` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 3.0.4-2.53.6.1 |
| `rsync` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 3.1.0-13.10.1 |
| `rsync` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 3.1.0-13.10.1 |
| `rsync` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 3.1.0-13.10.1 |
| `rsync` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 3.0.4-2.53.6.1 |
| `rsync` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 3.1.0-13.10.1 |
| `rsync` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 3.1.0-13.10.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Samba Rsync.

## How do I fix CVE-2018-5764?

Upgrade to a fixed version.

## Is CVE-2018-5764 being exploited?

There is no known exploitation of CVE-2018-5764 in the wild and no public exploit code.

Public exploit code:

- SyncShield - Browser Extension to Detect Unsafe Rsync Commands (CVE-2018-5764) (github_poc): https://github.com/waleedadam360-web/SyncShield

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5764 and fix it if it is affected.

What it is: CVE-2018-5764 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 17 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-5764 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-5764/ (Markdown: https://insights.sbomify.com/CVE-2018-5764/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-5764
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-5764
- OSV: https://osv.dev/vulnerability/CVE-2018-5764

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-5764/
Summaries are generated and may contain mistakes; the official description above is the record.