Information disclosure via Apport screenrc attachment
Published Apr 17, 2020 · Updated Sep 17, 2024
Information disclosure in Byobu before 5.128-0ubuntu1 allows remote attackers to obtain sensitive .screenrc contents through Apport. The source_byobu.py package hook attaches the local user's .screenrc to an Apport crash report without excluding configuration secrets. Exposure requires the local user to submit the generated report; disclosed data can include private hostnames, usernames, and passwords.
Summary
What happened
Information disclosure in Byobu before 5.128-0ubuntu1 allows remote attackers to obtain sensitive .screenrc contents through Apport. The source_byobu.py package hook attaches the local user's .screenrc to an Apport crash report without excluding configuration secrets. Exposure requires the local user to submit the generated report; disclosed data can include private hostnames, usernames, and passwords.
The record
- CVE
- CVE-2019-7306
- Published
- Apr 17, 2020
- Updated
- Sep 17, 2024
- Vendor
- Canonical
- Product
- Byobu
- Classifications
- CWE-552
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <5.128-0ubuntu1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo