Homepage

Loop with Unreachable Exit Condition ('Infinite Loop') Affecting jbcs-httpd24-httpd-manual package, versions <0:2.4.37-80.jbcs.el7

Severity

 Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
2.14% (90th 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-3639697
  • published16 Mar 2022
  • disclosed15 Mar 2022
Report a new vulnerability Found a mistake?

Introduced: 15 Mar 2022

CVE-2022-0778  (opens in a new tab)
CWE-835  (opens in a new tab)

How to fix?

Upgrade RHEL:7 jbcs-httpd24-httpd-manual to version 0:2.4.37-80.jbcs.el7 or higher.
This issue was patched in RHSA-2022:1389.

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.

The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).

References

CVSS Scores

version 3.1