Improperly Implemented Security Check for Standard Affecting python2-pexpect package, versions <0:4.6-1.el7at


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

Exploit Maturity
Not Defined
EPSS
0.58% (79th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-PYTHON2PEXPECT-6585409
  • published7 Apr 2024
  • disclosed1 Jul 2019

Introduced: 1 Jul 2019

CVE-2019-12781  (opens in a new tab)
CWE-358  (opens in a new tab)
CWE-444  (opens in a new tab)

How to fix?

Upgrade RHEL:7 python2-pexpect to version 0:4.6-1.el7at or higher.
This issue was patched in RHSA-2020:4366.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python2-pexpect package and not the python2-pexpect package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.