CVE-2019-7307 | Apport contains a TOCTTOU vulnerability when reading the users ~/.apport-ignore.xml

Exp

Apport before versions 2.14.1-0ubuntu3.29+esm1, 2.20.1-0ubuntu2.19, 2.20.9-0ubuntu7.7, 2.20.10-0ubuntu27.1, 2.20.11-0ubuntu5 contained a TOCTTOU vulnerability when reading the users ~/.apport-ignore.xml file, which allows a local attacker to replace this file with a symlink to any other file on the system and so cause Apport to include the contents of this other file in the resulting crash report. The crash report could then be read by that user either by causing it to be uploaded and reported to Launchpad, or by leveraging some other vulnerability to read the resulting crash report, and so allow the user to read arbitrary files on the system.

Published: 2019-08-29 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-7307 is rated Exploit Available (52.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.10%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2019-7307

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-7307

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-26 0.04% 0.10% +0.05%
2 2023-03-07 0.89% 0.04% -0.84%
3 2022-04-01 — 0.89% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-7307

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.0 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 5.9 [email protected]
6.5 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.0 4.0 [email protected]
4.4 2.0 MEDIUM
AV:L/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 3.4 6.4 [email protected]

Weakness enumeration for CVE-2019-7307

OS Trackers for CVE-2019-7307

vendor priority summary link
suse low CVE-2019-7307 severity low: SUSE including 3 source package names (apport-0.114-12.8.6.1, apport-crashdb-sle-0.114-0.8.6.1, apport-gtk-0.114-12.8.6.1), 6 product×package rows across 2 product lines (SUSE Linux Enterprise Server 11 SP1-TERADATA, SUSE Linux Enterprise Server 11 SP3-TERADATA): Fixed 6. https://www.suse.com/security/cve/CVE-2019-7307/
ubuntu medium CVE-2019-7307 medium priority: Ubuntu including 1 source packages (apport), 6 status rows across 6 suites (bionic, cosmic, disco, trusty, upstream, xenial): released 5, needs-triage 1. https://ubuntu.com/security/CVE-2019-7307

Affected software / configurations for CVE-2019-7307

Vendor Product Version Raw CPE
apport_project apport 2.14.1 cpe:2.3:a:apport_project:apport:2.14.1:*:*:*:*:*:*:*
apport_project apport 2.20.1 cpe:2.3:a:apport_project:apport:2.20.1:*:*:*:*:*:*:*
apport_project apport 2.20.9 cpe:2.3:a:apport_project:apport:2.20.9:*:*:*:*:*:*:*
apport_project apport 2.20.10 cpe:2.3:a:apport_project:apport:2.20.10:*:*:*:*:*:*:*

References for CVE-2019-7307

cvelogic Threat Intelligence