CVE-2016-9949

Exp

An issue was discovered in Apport before 2.20.4. In apport/ui.py, Apport reads the CrashDB field and it then evaluates the field as Python code if it begins with a "{". This allows remote attackers to execute arbitrary Python code.

Published: 2016-12-16 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-9949 is rated High Exploit Risk (85.1/100): CVSS High severity, with high exploitation likelihood (EPSS 17.73%, 97th percentile). 2 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +7.92% over the last day, indicating growing attacker interest. 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-2016-9949

EDB-ID Source Kind Published Link
40937 exploit_db edb 2016-12-14 Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2016-9949

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-06-15 9.81% 17.73% +7.92%
2 2026-01-14 9.74% 9.81% +0.07%
3 2025-12-28 — 9.74% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-9949

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.8 5.9 [email protected]
9.3 2.0 HIGH
AV:N/AC:M/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 8.6 10.0 [email protected]

Weakness enumeration for CVE-2016-9949

OS Trackers for CVE-2016-9949

vendor priority summary link
ubuntu medium CVE-2016-9949 medium priority: Ubuntu including 1 source packages (apport), 6 status rows across 6 suites (precise, trusty, upstream, xenial, yakkety, zesty): released 3, not-affected 2, needs-triage 1. https://ubuntu.com/security/CVE-2016-9949

Affected software / configurations for CVE-2016-9949

Vendor Product Version Raw CPE
apport_project apport <= 2.20.3 cpe:2.3:a:apport_project:apport:*:*:*:*:*:*:*:*
canonical ubuntu_linux <= 12.10 cpe:2.3:o:canonical:ubuntu_linux:*:*:*:*:*:*:*:*

References for CVE-2016-9949

cvelogic Threat Intelligence