libarchive 3.2.2 archive_read_support_format_lha.c lha_read_file_header_1 out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.2$0-$5k0.00

Summaryinfo

A vulnerability was found in libarchive 3.2.2. It has been rated as critical. This issue affects the function lha_read_file_header_1 of the file archive_read_support_format_lha.c. Performing a manipulation results in out-of-bounds. This vulnerability was named CVE-2017-5601. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in libarchive 3.2.2 (File Compression Software). It has been classified as critical. This affects the function lha_read_file_header_1 of the file archive_read_support_format_lha.c. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

An error in the lha_read_file_header_1() function (archive_read_support_format_lha.c) in libarchive 3.2.2 allows remote attackers to trigger an out-of-bounds read memory access and subsequently cause a crash via a specially crafted archive.

The bug was discovered 01/27/2017. The weakness was presented 01/27/2017 by Jakub Jirasek with Secunia as SA74169 as confirmed mailinglist post (Bugtraq). It is possible to read the advisory at seclists.org. The public release was coordinated in cooperation with the project team. This vulnerability is uniquely identified as CVE-2017-5601 since 01/27/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability was handled as a non-public zero-day exploit for at least 21 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 96909 (Debian DLA-810-1 : libarchive security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176840 (Debian Security Update for libarchive (DLA 1600-1)).

Upgrading eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (96909), SecurityFocus (BID 95837†), Secunia (SA74169†) and SecurityTracker (ID 1037974†). See VDB-91754, VDB-95905, VDB-95915 and VDB-95929 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.4
VulDB Meta Temp Score: 7.2

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 96909
Nessus Name: Debian DLA-810-1 : libarchive security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 841810
OpenVAS Name: Ubuntu Update for libarchive USN-3225-1
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍

Patch: github.com

Timelineinfo

12/29/2016 🔍
01/16/2017 +18 days 🔍
01/19/2017 +3 days 🔍
01/27/2017 +8 days 🔍
01/27/2017 +0 days 🔍
01/27/2017 +0 days 🔍
01/27/2017 +0 days 🔍
01/27/2017 +0 days 🔍
01/28/2017 +1 days 🔍
02/01/2017 +4 days 🔍
03/09/2017 +36 days 🔍
05/16/2026 +3355 days 🔍

Sourcesinfo

Product: github.com

Advisory: SA74169
Researcher: Jakub Jirasek
Organization: Secunia
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2017-5601 (🔍)
GCVE (CVE): GCVE-0-2017-5601
GCVE (VulDB): GCVE-100-96243
SecurityFocus: 95837 - libarchive 'lha_read_file_header_1()' Function Memory Corruption Vulnerability
Secunia: 74169
OSVDB: - CVE-2017-5601 - libarchive - Out-of-Bounds Read Issue
SecurityTracker: 1037974

See also: 🔍

Entryinfo

Created: 01/28/2017 09:21
Updated: 05/16/2026 11:08
Changes: 01/28/2017 09:21 (89), 08/19/2020 16:13 (5), 11/04/2022 15:58 (4), 05/16/2026 11:08 (15)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!