# CVE-2019-3500: Information disclosure in n/a

> Local attackers can read HTTP Basic Authentication credentials from log files when the logging feature is enabled in aria2.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2019-3500, DEBIAN-CVE-2019-3500, DLA-1636-1, DLA-2873-1, GHSA-g768-79g3-c28j, MGASA-2019-0036, UBUNTU-CVE-2019-3500, USN-4869-1, openSUSE-SU-2019:0050-1, openSUSE-SU-2021:1125-1, openSUSE-SU-2024:10631-1

## What is CVE-2019-3500?

CVE-2019-3500 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 2 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

aria2c in aria2 1.33.1, when --log is used, can store an HTTP Basic Authentication username and password in a file, which might allow local users to obtain sensitive information by reading this file.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2019-3500?

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aria2` | SUSE:Package Hub 15 | All versions | 1.33.1-bp150.3.7.1 |
| `aria2` | SUSE:Package Hub 15 SP1 | All versions | 1.35.0-bp153.2.3.1 |
| `aria2` | SUSE:Package Hub 15 SP2 | All versions | 1.35.0-bp153.2.3.1 |
| `aria2` | SUSE:Package Hub 15 SP3 | All versions | 1.35.0-bp153.2.3.1 |
| `aria2` | openSUSE:Leap 15.0 | All versions | 1.33.1-bp150.3.7.1 |
| `aria2` | openSUSE:Leap 15.2 | All versions | 1.35.0-bp153.2.3.1 |
| `aria2` | openSUSE:Leap 15.3 | All versions | 1.35.0-bp153.2.3.1 |
| `aria2` | openSUSE:Tumbleweed | All versions | 1.36.0-1.2 |

Products: Aria2 Project Aria2, Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora.

## How do I fix CVE-2019-3500?

Apply the vendor's patch.

## Is CVE-2019-3500 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2026-8367](https://insights.sbomify.com/CVE-2026-8367/): aria2c Improper Certificate Validation (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3500 and fix it if it is affected.

What it is: CVE-2019-3500 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 2 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-3500 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-2019-3500/ (Markdown: https://insights.sbomify.com/CVE-2019-3500/index.md)
```

## Sources

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

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