# CVE-2019-7306: Byobu apport hook uploads user's ~/.screenrc

> Byobu's Apport hook automatically uploads the user's .screenrc file, potentially exposing sensitive credentials and hostnames to support servers.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Apr 2020
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2019-7306, GHSA-2rpx-jj49-wf29, UBUNTU-CVE-2019-7306, USN-5234-1

## What is CVE-2019-7306?

CVE-2019-7306 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 17 Apr 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Byobu Apport hook may disclose sensitive information since it automatically uploads the local user's .screenrc which may contain private hostnames, usernames and passwords. This issue affects: byobu

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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

It affects 2 products.


Products: Byobu Byobu, Canonical Ubuntu Linux.

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

Apply the vendor's patch.

## Is CVE-2019-7306 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-7306 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 17 Apr 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-7306 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-7306/ (Markdown: https://insights.sbomify.com/CVE-2019-7306/index.md)
```

## Sources

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

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