Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

redhat логотип

CVE-2020-7061

Опубликовано: 26 янв. 2020
Источник: redhat
CVSS3: 9.1

Описание

In PHP versions 7.3.x below 7.3.15 and 7.4.x below 7.4.3, while extracting PHAR files on Windows using phar extension, certain content inside PHAR file could lead to one-byte read past the allocated buffer. This could potentially lead to information disclosure or crash.

Отчет

This flaw affects only PHP running on Windows operating system.

Затронутые пакеты

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat Enterprise Linux 5phpNot affected
Red Hat Enterprise Linux 5php53Not affected
Red Hat Enterprise Linux 6phpNot affected
Red Hat Enterprise Linux 7phpNot affected
Red Hat Enterprise Linux 8php:7.2/phpNot affected
Red Hat Enterprise Linux 8php:7.3/phpNot affected
Red Hat Software Collectionsrh-php72-phpNot affected
Red Hat Software Collectionsrh-php73-phpNot affected

Показывать по

Дополнительная информация

Статус:

Low
Дефект:
CWE-122
https://bugzilla.redhat.com/show_bug.cgi?id=1808529php: heap-based buffer overflow in phar_extract_file

9.1 Critical

CVSS3

Связанные уязвимости

CVSS3: 6.5
ubuntu
почти 6 лет назад

In PHP versions 7.3.x below 7.3.15 and 7.4.x below 7.4.3, while extracting PHAR files on Windows using phar extension, certain content inside PHAR file could lead to one-byte read past the allocated buffer. This could potentially lead to information disclosure or crash.

CVSS3: 6.5
nvd
почти 6 лет назад

In PHP versions 7.3.x below 7.3.15 and 7.4.x below 7.4.3, while extracting PHAR files on Windows using phar extension, certain content inside PHAR file could lead to one-byte read past the allocated buffer. This could potentially lead to information disclosure or crash.

CVSS3: 6.5
debian
почти 6 лет назад

In PHP versions 7.3.x below 7.3.15 and 7.4.x below 7.4.3, while extrac ...

CVSS3: 9.1
github
больше 3 лет назад

In PHP versions 7.3.x below 7.3.15 and 7.4.x below 7.4.3, while extracting PHAR files on Windows using phar extension, certain content inside PHAR file could lead to one-byte read past the allocated buffer. This could potentially lead to information disclosure or crash.

9.1 Critical

CVSS3