Security readout for executives and security teams
Plain-English summary
This vulnerability can crash software that uses libarchive 3.3.2 when it processes a specially crafted XAR archive. The known impact is denial of service, not data theft or code execution based on the provided sources.
Executive priority
Treat this as a targeted availability risk. Prioritize exposed archive-processing services and automated ingestion pipelines, but it is not supported as actively exploited or code-execution capable by the provided evidence.
Technical view
CVE-2017-14166 is a heap-based buffer over-read in libarchive's XAR reader, tied to mishandling empty strings in atol8 within archive_read_support_format_xar.c. A crafted XAR archive can trigger xml_data processing failure and application crash.
Likely exposure
Exposure is most likely where libarchive 3.3.2 processes untrusted archives, such as upload handlers, scanners, extraction services, package workflows, or desktop tools. The source bundle does not identify specific downstream products beyond libarchive and distribution packages.
Exploitation context
The CVE describes remote attackers using a crafted XAR archive to cause a crash. CISA KEV status is false in the bundle, and no provided source states active exploitation in the wild.
Researcher notes
Source wording identifies a heap-based buffer over-read, while one Gentoo reference title says buffer overflow. Keep analysis anchored to the CVE description and upstream fix until vendor advisories provide more detail.
Mitigation direction
- Update libarchive through the relevant vendor security channel.
- Apply Debian, Ubuntu, or Gentoo security updates where those distributions are in use.
- Check upstream libarchive guidance and the referenced fix commit for source-built deployments.
- Reduce exposure by limiting untrusted XAR archive processing where updates are delayed.
Validation and detection
- Inventory systems and applications using libarchive 3.3.2.
- Confirm distribution packages include the cited Debian, Ubuntu, or Gentoo security update.
- For source builds, verify the upstream fix commit is present.
- Review archive-processing entry points for untrusted XAR input.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2017-14166 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://blogs.gentoo.org/ago/2017/09/06/libarchive-heap-based-buffer-overflow-in-xml_data-archive_read_support_format_xar-c/CVE reference · x_refsource_MISC
- [debian-lts-announce] 20181129 [SECURITY] [DLA 1600-1] libarchive security updateCVE reference · mailing-list, x_refsource_MLIST
- DSA-4360CVE reference · vendor-advisory, x_refsource_DEBIAN
- https://github.com/libarchive/libarchive/commit/fa7438a0ff4033e4741c807394a9af6207940d71CVE reference · x_refsource_MISC
- USN-3736-1CVE reference · vendor-advisory, x_refsource_UBUNTU
- GLSA-201908-11CVE reference · vendor-advisory, x_refsource_GENTOO
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
