Поиск уязвимостей
Количество 17
Количество 17
ALT-PU-2026-13062
ALT-PU-2026-13062: package `unrar` update to version 7.2.7-alt1
ALT-PU-2026-12706
ALT-PU-2026-12706: package `unrar` update to version 7.2.7-alt1
CVE-2022-48579
UnRAR before 6.2.3 allows extraction of files outside of the destination folder via symlink chains.
CVE-2022-48579
UnRAR before 6.2.3 allows extraction of files outside of the destination folder via symlink chains.
CVE-2022-48579
UnRAR before 6.2.3 allows extraction of files outside of the destination folder via symlink chains.
CVE-2022-48579
UnRAR before 6.2.3 allows extraction of files outside of the destinati ...
CVE-2026-14191
An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) parser in WinRAR and UnRAR (RecVolumes5::ReadHeader in recvol5.cpp). The RecItems vector is sized only when the first .rev file in a set is processed; subsequent .rev files supply an independent RecNum value that is validated against that file's own TotalCount field but never against the actual size of RecItems. A crafted set of two or more .rev files can therefore write an attacker-controlled 32-bit value (the header's RevCRC field) to RecItems[RecNum] at an attacker-controlled offset up to 65534 * sizeof(RecVolItem) bytes past the allocation, corrupting adjacent heap objects. Triggering requires the victim to run a recovery/test operation on an attacker-supplied .rev set (for example 'unrar t x.part1.rev', WinRAR 'Repair archive', or auto-recovery when extracting a volume set with a missing .rar part). This is the RAR5-path sibling of CVE-2023-40477 (which was fixed in the RAR3 path only in WinRAR 6.23). Fixed i...
CVE-2026-14191
An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) parser in WinRAR and UnRAR (RecVolumes5::ReadHeader in recvol5.cpp). The RecItems vector is sized only when the first .rev file in a set is processed; subsequent .rev files supply an independent RecNum value that is validated against that file's own TotalCount field but never against the actual size of RecItems. A crafted set of two or more .rev files can therefore write an attacker-controlled 32-bit value (the header's RevCRC field) to RecItems[RecNum] at an attacker-controlled offset up to 65534 * sizeof(RecVolItem) bytes past the allocation, corrupting adjacent heap objects. Triggering requires the victim to run a recovery/test operation on an attacker-supplied .rev set (for example 'unrar t x.part1.rev', WinRAR 'Repair archive', or auto-recovery when extracting a volume set with a missing .rar part). This is the RAR5-path sibling of CVE-2023-40477 (which was fixed in the RAR3 path only in WinRAR 6.23). Fixed in W
CVE-2026-14191
WinRAR / UnRAR RAR5 recovery-volume (.rev) out-of-bounds heap write in RecVolumes5::ReadHeader
CVE-2026-14191
An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) ...
GHSA-pg3x-qpq9-p4v6
UnRAR before 6.2.3 allows extraction of files outside of the destination folder via symlink chains.
BDU:2023-07638
Уязвимость средства разархивирования файлов UnRAR, связанная с неверным определением символических ссылок перед доступом к файлу, позволяющая нарушителю получить доступ к конфиденциальным данным
GHSA-5hjj-fvq6-8j36
An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) parser in WinRAR and UnRAR (RecVolumes5::ReadHeader in recvol5.cpp). The RecItems vector is sized only when the first .rev file in a set is processed; subsequent .rev files supply an independent RecNum value that is validated against that file's own TotalCount field but never against the actual size of RecItems. A crafted set of two or more .rev files can therefore write an attacker-controlled 32-bit value (the header's RevCRC field) to RecItems[RecNum] at an attacker-controlled offset up to 65534 * sizeof(RecVolItem) bytes past the allocation, corrupting adjacent heap objects. Triggering requires the victim to run a recovery/test operation on an attacker-supplied .rev set (for example 'unrar t x.part1.rev', WinRAR 'Repair archive', or auto-recovery when extracting a volume set with a missing .rar part). This is the RAR5-path sibling of CVE-2023-40477 (which was fixed in the RAR3 path only in WinRAR 6.23). Fixed i...
BDU:2026-09733
Уязвимость системы обработки восстановления томов RAR5 файлового архиватора WinRAR и средства разархивирования файлов UnRAR, позволяющая нарушителю выполнить произвольный код
ROS-20230911-08
Уязвимость UnRAR
ROS-20260907-80-0025
Уязвимость unrar
ROS-20260907-73-0024
Уязвимость unrar
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
ALT-PU-2026-13062 ALT-PU-2026-13062: package `unrar` update to version 7.2.7-alt1 | CVSS3: 7.8 | 3 месяца назад | ||
ALT-PU-2026-12706 ALT-PU-2026-12706: package `unrar` update to version 7.2.7-alt1 | CVSS3: 7.8 | 3 месяца назад | ||
CVE-2022-48579 UnRAR before 6.2.3 allows extraction of files outside of the destination folder via symlink chains. | CVSS3: 7.5 | 1% Низкий | больше 3 лет назад | |
CVE-2022-48579 UnRAR before 6.2.3 allows extraction of files outside of the destination folder via symlink chains. | CVSS3: 7.5 | 1% Низкий | больше 3 лет назад | |
CVE-2022-48579 UnRAR before 6.2.3 allows extraction of files outside of the destination folder via symlink chains. | CVSS3: 7.5 | 1% Низкий | около 3 лет назад | |
CVE-2022-48579 UnRAR before 6.2.3 allows extraction of files outside of the destinati ... | CVSS3: 7.5 | 1% Низкий | больше 3 лет назад | |
CVE-2026-14191 An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) parser in WinRAR and UnRAR (RecVolumes5::ReadHeader in recvol5.cpp). The RecItems vector is sized only when the first .rev file in a set is processed; subsequent .rev files supply an independent RecNum value that is validated against that file's own TotalCount field but never against the actual size of RecItems. A crafted set of two or more .rev files can therefore write an attacker-controlled 32-bit value (the header's RevCRC field) to RecItems[RecNum] at an attacker-controlled offset up to 65534 * sizeof(RecVolItem) bytes past the allocation, corrupting adjacent heap objects. Triggering requires the victim to run a recovery/test operation on an attacker-supplied .rev set (for example 'unrar t x.part1.rev', WinRAR 'Repair archive', or auto-recovery when extracting a volume set with a missing .rar part). This is the RAR5-path sibling of CVE-2023-40477 (which was fixed in the RAR3 path only in WinRAR 6.23). Fixed i... | CVSS3: 7.8 | 0% Низкий | 4 месяца назад | |
CVE-2026-14191 An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) parser in WinRAR and UnRAR (RecVolumes5::ReadHeader in recvol5.cpp). The RecItems vector is sized only when the first .rev file in a set is processed; subsequent .rev files supply an independent RecNum value that is validated against that file's own TotalCount field but never against the actual size of RecItems. A crafted set of two or more .rev files can therefore write an attacker-controlled 32-bit value (the header's RevCRC field) to RecItems[RecNum] at an attacker-controlled offset up to 65534 * sizeof(RecVolItem) bytes past the allocation, corrupting adjacent heap objects. Triggering requires the victim to run a recovery/test operation on an attacker-supplied .rev set (for example 'unrar t x.part1.rev', WinRAR 'Repair archive', or auto-recovery when extracting a volume set with a missing .rar part). This is the RAR5-path sibling of CVE-2023-40477 (which was fixed in the RAR3 path only in WinRAR 6.23). Fixed in W | CVSS3: 7.8 | 0% Низкий | 4 месяца назад | |
CVE-2026-14191 WinRAR / UnRAR RAR5 recovery-volume (.rev) out-of-bounds heap write in RecVolumes5::ReadHeader | 0% Низкий | 4 месяца назад | ||
CVE-2026-14191 An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) ... | CVSS3: 7.8 | 0% Низкий | 4 месяца назад | |
GHSA-pg3x-qpq9-p4v6 UnRAR before 6.2.3 allows extraction of files outside of the destination folder via symlink chains. | CVSS3: 7.5 | 1% Низкий | больше 3 лет назад | |
BDU:2023-07638 Уязвимость средства разархивирования файлов UnRAR, связанная с неверным определением символических ссылок перед доступом к файлу, позволяющая нарушителю получить доступ к конфиденциальным данным | CVSS3: 7.5 | 1% Низкий | почти 4 года назад | |
GHSA-5hjj-fvq6-8j36 An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) parser in WinRAR and UnRAR (RecVolumes5::ReadHeader in recvol5.cpp). The RecItems vector is sized only when the first .rev file in a set is processed; subsequent .rev files supply an independent RecNum value that is validated against that file's own TotalCount field but never against the actual size of RecItems. A crafted set of two or more .rev files can therefore write an attacker-controlled 32-bit value (the header's RevCRC field) to RecItems[RecNum] at an attacker-controlled offset up to 65534 * sizeof(RecVolItem) bytes past the allocation, corrupting adjacent heap objects. Triggering requires the victim to run a recovery/test operation on an attacker-supplied .rev set (for example 'unrar t x.part1.rev', WinRAR 'Repair archive', or auto-recovery when extracting a volume set with a missing .rar part). This is the RAR5-path sibling of CVE-2023-40477 (which was fixed in the RAR3 path only in WinRAR 6.23). Fixed i... | CVSS3: 7.8 | 0% Низкий | 4 месяца назад | |
BDU:2026-09733 Уязвимость системы обработки восстановления томов RAR5 файлового архиватора WinRAR и средства разархивирования файлов UnRAR, позволяющая нарушителю выполнить произвольный код | CVSS3: 7.8 | 0% Низкий | 4 месяца назад | |
ROS-20230911-08 Уязвимость UnRAR | CVSS3: 7.5 | 1% Низкий | около 3 лет назад | |
ROS-20260907-80-0025 Уязвимость unrar | CVSS3: 7.8 | 0% Низкий | 2 месяца назад | |
ROS-20260907-73-0024 Уязвимость unrar | CVSS3: 7.8 | 0% Низкий | 2 месяца назад |
Уязвимостей на страницу