Authentication Bypass Affecting jbcs-httpd24-httpd-manual package, versions <0:2.4.37-74.jbcs.el7


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.36% (73rd 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-JBCSHTTPD24HTTPDMANUAL-3639589
  • published1 Nov 2021
  • disclosed31 Mar 2021

Introduced: 31 Mar 2021

CVE-2021-22890  (opens in a new tab)
CWE-290  (opens in a new tab)

How to fix?

Upgrade RHEL:7 jbcs-httpd24-httpd-manual to version 0:2.4.37-74.jbcs.el7 or higher.
This issue was patched in RHSA-2021:2472.

NVD Description

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

curl 7.63.0 to and including 7.75.0 includes vulnerability that allows a malicious HTTPS proxy to MITM a connection due to bad handling of TLS 1.3 session tickets. When using a HTTPS proxy and TLS 1.3, libcurl can confuse session tickets arriving from the HTTPS proxy but work as if they arrived from the remote server and then wrongly "short-cut" the host handshake. When confusing the tickets, a HTTPS proxy can trick libcurl to use the wrong session ticket resume for the host and thereby circumvent the server TLS certificate check and make a MITM attack to be possible to perform unnoticed. Note that such a malicious HTTPS proxy needs to provide a certificate that curl will accept for the MITMed server for an attack to work - unless curl has been told to ignore the server certificate check.

CVSS Scores

version 3.1