Information Exposure Affecting jbcs-httpd24-httpd-manual package, versions <0:2.4.37-52.jbcs.el7


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
2.71% (91st 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-3624467
  • published26 Jul 2021
  • disclosed10 Sept 2019

Introduced: 10 Sep 2019

CVE-2019-1549  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade RHEL:7 jbcs-httpd24-httpd-manual to version 0:2.4.37-52.jbcs.el7 or higher.
This issue was patched in RHSA-2020:1337.

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.

OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

References

CVSS Scores

version 3.1