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

exploitDog

altlinux логотип

ALT-PU-2021-1412

Критический

ALT-PU-2021-1412: package python3 update to version 3.9.2-alt1

Источник
errata.altlinux.org
Дата публикации
27.02.2021
Дата обновления
27.02.2021
Устраненные уязвимости
4

ALT Linux branch p11
ALT Container
ALT Education
ALT Workstation
ALT Workstation K
ALT Server
ALT Virtualization PVE Edition
ALT Linux branch p10
ALT Server
ALT Virtualization Server
ALT Workstation
ALT Workstation K
ALT Education
Simply Linux
Starterkit
ALT Container

Описание

This update upgrades python3 to version 3.9.2-alt1.

Устраненные уязвимости4

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

oracle-oval
больше 5 лет назад

ELSA-2021-1633: python3 security update (MODERATE)

CVSS3: 9.8
altlinux
около 5 лет назад

ALT-PU-2021-2478: package `python` update to version 2.7.18-alt6

CVSS3: 9.8
altlinux
больше 5 лет назад

ALT-PU-2021-2420: package `python` update to version 2.7.18-alt6

CVSS3: 5.9
ubuntu
больше 5 лет назад

The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9.0 and before 3.9.2 are vulnerable to Web Cache Poisoning via urllib.parse.parse_qsl and urllib.parse.parse_qs by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not include it in a cache key of an unkeyed parameter.

CVSS3: 5.9
redhat
больше 5 лет назад

The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9.0 and before 3.9.2 are vulnerable to Web Cache Poisoning via urllib.parse.parse_qsl and urllib.parse.parse_qs by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not include it in a cache key of an unkeyed parameter.