Improperly Implemented Security Check for Standard Affecting tfm-runtime package, versions <0:6.1-1.el7sat


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
1.12% (86th 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-TFMRUNTIME-5375286
  • published26 Mar 2023
  • 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 tfm-runtime to version 0:6.1-1.el7sat or higher.
This issue was patched in RHSA-2020:4366.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tfm-runtime package and not the tfm-runtime 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.