CVE Vulnerabilities

CVE-2018-13410

Use After Free

Published: Jul 06, 2018 | Modified: May 17, 2024
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu
LOW

Info-ZIP Zip 3.0, when the -T and -TT command-line options are used, allows attackers to cause a denial of service (invalid free and application crash) or possibly have unspecified other impact because of an off-by-one error. NOTE: it is unclear whether there are realistic scenarios in which an untrusted party controls the -TT value, given that the entire purpose of -TT is execution of arbitrary commands

Weakness

Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.

Affected Software

Name Vendor Start Version End Version
Zip Info-zip_project 3.0 (including) 3.0 (including)
Zip Ubuntu artful *
Zip Ubuntu bionic *
Zip Ubuntu cosmic *
Zip Ubuntu devel *
Zip Ubuntu disco *
Zip Ubuntu eoan *
Zip Ubuntu esm-infra-legacy/trusty *
Zip Ubuntu esm-infra/bionic *
Zip Ubuntu esm-infra/xenial *
Zip Ubuntu focal *
Zip Ubuntu groovy *
Zip Ubuntu hirsute *
Zip Ubuntu impish *
Zip Ubuntu jammy *
Zip Ubuntu precise/esm *
Zip Ubuntu trusty *
Zip Ubuntu trusty/esm *
Zip Ubuntu xenial *

Extended Description

The use of previously-freed memory can have any number of adverse consequences, ranging from the corruption of valid data to the execution of arbitrary code, depending on the instantiation and timing of the flaw. The simplest way data corruption may occur involves the system’s reuse of the freed memory. Use-after-free errors have two common and sometimes overlapping causes:

In this scenario, the memory in question is allocated to another pointer validly at some point after it has been freed. The original pointer to the freed memory is used again and points to somewhere within the new allocation. As the data is changed, it corrupts the validly used memory; this induces undefined behavior in the process. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Potential Mitigations

References