LiveActive security incident?Get immediate response
CVE Record

CVE-2020-15701: Unhandled exception in apport

An unhandled exception in check_ignored() in apport/report.py can be exploited by a local attacker to cause a denial of service. If the mtime attribute is a string value in apport-ignore.xml, it will trigger an unhandled exception, resulting in a crash. Fixed in 2.20.1-0ubuntu2.24, 2.20.9-0ubuntu7.16, 2.20.11-0ubuntu27.6.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-15701 is a local denial-of-service issue in Ubuntu's apport crash-reporting tool. A low-privileged local attacker could make apport crash, disrupting crash reporting. The sources do not indicate data theft, privilege escalation, remote access, or active exploitation.

Executive priority

Treat this as a moderate operational reliability issue, not an emergency breach indicator. Patch through normal Ubuntu security update processes, with priority for shared systems where local misuse is plausible.

Technical view

apport/report.py check_ignored() mishandles an apport-ignore.xml mtime attribute when it is a string, causing an unhandled exception and crash. CVSS 3.1 is 5.5 with local attack vector, low complexity, low privileges, no user interaction, and high availability impact.

Likely exposure

Exposure is mainly Ubuntu systems running affected apport builds: 2.20.1, 2.20.9, or 2.20.11. The vulnerability requires local access, so risk is higher on shared servers, developer workstations, kiosks, or environments with untrusted local users.

Exploitation context

The provided sources describe local denial of service only. KEV is false, and the bundle provides no evidence of active exploitation. The triggering condition involves malformed apport ignore metadata, but no public exploit status is cited here.

Researcher notes

The evidence supports CWE-755 improper handling of exceptional conditions. The impact is apport availability, with no cited confidentiality or integrity impact. The source bundle does not identify affected Ubuntu release names beyond package build lines.

Mitigation direction

  • Update apport to the fixed Ubuntu build listed for your release.
  • Use Ubuntu USN-4449-1 and USN-4449-2 as authoritative patch guidance.
  • Prioritize shared or multi-user Ubuntu systems before single-user endpoints.
  • If patch state is unclear, check current Canonical guidance before applying workarounds.

Validation and detection

  • Inventory Ubuntu systems running apport package versions 2.20.1, 2.20.9, or 2.20.11.
  • Confirm apport is fixed at 2.20.1-0ubuntu2.24, 2.20.9-0ubuntu7.16, or 2.20.11-0ubuntu27.6.
  • Verify affected systems receive the relevant Ubuntu security update.
  • Review local-user exposure on systems where apport remains unpatched.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-755: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-15701 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2020-15701Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Canonicalapport2.20.1, 2.20.9, 2.20.11Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-755 · source CWE mapping

Improper Handling of Exceptional Conditions

Improper Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.