Vulnérabilités / openSUSE-SU-2017:1658-1

critique

openSUSE-SU-2017:1658-1

Security update for unrar

Dans la Trivy database depuis au moins le 24 oct. 2026, 07:11 UTCLa date d'entrée avant ce build n'est pas enregistrée.

Sévérité par source

Aucune source ne donne de score CVSS.

Le label propre à Trivy est CRITICAL. Critique selon SUSE.

Description

This update for unrar to version 5.5 fixes the following issues: Version 5.5.5 * CVE-2012-6706: fixes VMSF_DELTA memory corruption (boo#1045315) see https://bugs.chromium.org/p/project-zero/issues/detail?id=1286&can=1&q=unrar&desc=2 Version 5.5.1 * Based on RAR 5.50 beta1 * Added extraction support for .LZ archives created by Lzip compressor. * Modern TAR tools can store high precision file times, lengthy file names and large file sizes in special PAX extended headers inside of TAR archive. Now WinRAR supports such PAX headers and uses them when extracting TAR archives. * unrar no longer fails to unpack files in ZIP archives compressed with XZ algorithm and encrypted with AES Version 5.4.5. * Based on final RAR 5.40. * If RAR recovery volumes (.rev files) are present in the same folder as usual RAR volumes, archive test command verifies .rev contents after completing testing .rar files. If you wish to test only .rev files without checking .rar volumes, you can run: `unrar t arcname.part1.rev`. * If -p switch is used without optional <pwd> parameter, a password can be also set with file redirection or pipe. * unrar treats 'arcname.partN' as 'arcname.partN.rar' if 'arcname.partN' does not exist and 'arcname.part#.rar' exists. For example, it is allowed to run: `unrar x arcname.part01` to start extraction from 'arcname.part01.rar'.

Paquets affectés et versions corrigées

SourcePaquetCorrigé en
openSUSE Leap 42.2libunrar-devel, libunrar5_5_5, unrar5.5.5-3.1
Afficher les 3 entrées d'une source
SourcePaquetCorrigé en
openSUSE Leap 42.2libunrar-devel5.5.5-3.1
openSUSE Leap 42.2libunrar5_5_55.5.5-3.1
openSUSE Leap 42.2unrar5.5.5-3.1

Références

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.