LiveActive security incident?Get immediate response
CVE Record

CVE-2017-10708: An issue was discovered in Apport through 2.20.x.

An issue was discovered in Apport through 2.20.x. In apport/report.py, Apport sets the ExecutablePath field and it then uses the path to run package specific hooks without protecting against path traversal. This allows remote attackers to execute arbitrary code via a crafted .crash file.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Apport, a crash-reporting component, can be tricked by a crafted crash file into running unintended code. The provided sources describe arbitrary code execution but do not provide CVSS, confirmed affected distributions, or active exploitation evidence.

Executive priority

Prioritize if Apport is installed on user-facing or support systems that may process external crash reports. Arbitrary code execution is business-relevant, but urgency is tempered by missing exploit and affected-environment detail.

Technical view

In apport/report.py, Apport sets ExecutablePath from a crash report and later uses that path to run package-specific hooks without path traversal protection. A crafted .crash file can abuse this behavior to execute arbitrary code.

Likely exposure

Systems running Apport through 2.20.x are the stated exposure. Practical risk depends on whether those systems process attacker-supplied .crash files. The bundle does not identify specific vendor packages, distributions, or fixed versions.

Exploitation context

The bundle does not cite CISA KEV or active exploitation. It states remote attackers can execute arbitrary code via a crafted .crash file, but does not establish delivery path, required privileges, or real-world exploitation.

Researcher notes

Evidence is limited to the CVE description and Launchpad references. Confirm exact vulnerable and fixed package revisions from Ubuntu Launchpad before asserting distribution impact or remediation completeness.

Mitigation direction

  • Check Launchpad changelog and vendor advisories for fixed Apport packages.
  • Upgrade Apport to a vendor-supported fixed release when available.
  • Limit or disable processing of untrusted .crash files where operationally feasible.
  • Treat received .crash files as untrusted input until vendor guidance is applied.

Validation and detection

  • Inventory systems running Apport and record installed package versions.
  • Flag Apport versions through 2.20.x for vendor guidance review.
  • Review workflows that import or process externally supplied .crash files.
  • Confirm remediation against vendor changelog or advisory notes.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-10708 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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