CVE-2019-15790
Apport reads PID files with elevated privileges
Public exploit available. Not confirmed exploited in the wild yet. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- Canonical ApportAffected: ≥ 2.14.1, < 2.14.1-0ubuntu3.29+esm3Upgrade to: 2.14.1-0ubuntu3.29+esm3Affected: ≥ 2.20.1, < 2.20.1-0ubuntu2.22Upgrade to: 2.20.1-0ubuntu2.22Affected: ≥ 2.20.9, < 2.20.9-0ubuntu7.12Upgrade to: 2.20.9-0ubuntu7.12Affected: ≥ 2.20.11, < 2.20.11-0ubuntu8.6Upgrade to: 2.20.11-0ubuntu8.6Stated by: CVE record
- Canonical Ltd. UbuntuAffected: 16.04 LTSUpgrade to: not statedStated by: BDU
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
Apport reads and writes information on a crashed process to /proc/pid with elevated privileges. Apport then determines which user the crashed process belongs to by reading /proc/pid through get_pid_info() in data/apport. An unprivileged user could exploit this to read information about a privileged running process by exploiting PID recycling. This information could then be used to obtain ASLR offsets for a process with an existing memory corruption vulnerability. The initial fix introduced regressions in the Python Apport library due to a missing argument in Report.add_proc_environ in apport/report.py. It also caused an autopkgtest failure when reading /proc/pid and with Python 2 compatibility by reading /proc maps. The initial and subsequent regression fixes are in 2.20.11-0ubuntu16, 2.20.11-0ubuntu8.6, 2.20.9-0ubuntu7.12, 2.20.1-0ubuntu2.22 and 2.14.1-0ubuntu3.29+esm3.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
4 sources with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
0.5% chance of exploitation activity in the next 30 days, which ranks it in the 44th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
The patch came 123 days before any public exploit.
- OpenVAS check added
- Public exploit / PoCsource: packetstorm
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N
Scored 2.8 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity NoneNo integrity impact
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Ubuntu, not every advisory. This one: public exploit.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI