LiveActive security incident?Get immediate response
CVE Record

CVE-2017-14502: read_header in archive_read_support_format_rar.c in libarchive 3.3.2 suffers from an off-by-one error for U...

read_header in archive_read_support_format_rar.c in libarchive 3.3.2 suffers from an off-by-one error for UTF-16 names in RAR archives, leading to an out-of-bounds read in archive_read_format_rar_read_header.

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

Security readout for executives and security teams

Plain-English summary

CVE-2017-14502 is a libarchive bug in RAR archive handling. A malformed RAR filename using UTF-16 could make libarchive read past an expected buffer boundary. The source bundle does not provide a CVSS score, active exploitation evidence, or proof of code execution.

Executive priority

Treat this as a patch-management issue for archive-processing systems, not an emergency based on the provided evidence. Prioritize internet-facing or automated file-ingestion paths because they can encounter malicious archives without user intent.

Technical view

In libarchive 3.3.2, read_header in archive_read_support_format_rar.c has an off-by-one error for UTF-16 names. This leads to an out-of-bounds read in archive_read_format_rar_read_header. Public references include the upstream fix commit, OSS-Fuzz issue, and Linux distribution advisories.

Likely exposure

Systems are mainly exposed when libarchive or software linked to it processes untrusted RAR archives. Relevant places include file upload handling, email or malware scanning, backup extraction, archive indexing, and desktop/server tools that automatically inspect archives.

Exploitation context

The provided bundle marks KEV as false and includes no cited source showing active exploitation. OSS-Fuzz involvement suggests fuzz-discovered malformed archive parsing. The public data supports memory-safety impact during RAR parsing, but not exploitation in the wild.

Researcher notes

The strongest technical anchor is the upstream commit for an off-by-one in RAR UTF-16 filename handling. Severity metadata is incomplete in the bundle. Avoid assuming broader impact beyond out-of-bounds read unless confirmed by vendor analysis or local crash reproduction.

Mitigation direction

  • Update libarchive using vendor-supported packages or upstream fixed releases.
  • Prioritize services that parse user-supplied RAR files.
  • Consult Ubuntu, Debian, and Gentoo advisories for package-specific fixed versions.
  • Restrict or quarantine untrusted RAR processing until affected systems are patched.
  • Track embedded or statically linked libarchive copies separately from OS packages.

Validation and detection

  • Inventory hosts, containers, and applications using libarchive.
  • Check installed package versions against vendor advisories.
  • Identify workflows that automatically parse RAR archives from external users.
  • Confirm patched builds include the upstream fix or vendor backport.
  • Review scanner, upload, and extraction services for libarchive linkage.
Prepared
Confidence
medium
Sources
9

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.

cve · low confidence lookup

CVE-2017-14502 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
8Source 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.