Missing Required Cryptographic Step Affecting jws5-tomcat package, versions <0:9.0.21-10.redhat_4.1.el8jws


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
1.4% (87th 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-RHEL8-JWS5TOMCAT-4403660
  • published26 Jul 2021
  • disclosed26 Feb 2019

Introduced: 26 Feb 2019

CVE-2019-1559  (opens in a new tab)
CWE-325  (opens in a new tab)

How to fix?

Upgrade RHEL:8 jws5-tomcat to version 0:9.0.21-10.redhat_4.1.el8jws or higher.
This issue was patched in RHSA-2019:3929.

NVD Description

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

If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this to be exploitable "non-stitched" ciphersuites must be in use. Stitched ciphersuites are optimised implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q).

References

CVSS Scores

version 3.1