Use of a Broken or Risky Cryptographic Algorithm Affecting python-twisted-web package, versions <0:12.1.0-5.el7_2
Threat Intelligence
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 ID SNYK-RHEL7-PYTHONTWISTEDWEB-5364982
- published 27 Mar 2023
- disclosed 30 Mar 2012
Introduced: 30 Mar 2012
CVE-2018-5382 Open this link in a new tabHow to fix?
Upgrade RHEL:7 python-twisted-web to version 0:12.1.0-5.el7_2 or higher.
This issue was patched in RHSA-2018:2927.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python-twisted-web package and not the python-twisted-web package as distributed by RHEL.
See How to fix? for RHEL:7 relevant fixed versions and status.
The default BKS keystore use an HMAC that is only 16 bits long, which can allow an attacker to compromise the integrity of a BKS keystore. Bouncy Castle release 1.47 changes the BKS format to a format which uses a 160 bit HMAC instead. This applies to any BKS keystore generated prior to BC 1.47. For situations where people need to create the files for legacy reasons a specific keystore type "BKS-V1" was introduced in 1.49. It should be noted that the use of "BKS-V1" is discouraged by the library authors and should only be used where it is otherwise safe to do so, as in where the use of a 16 bit checksum for the file integrity check is not going to cause a security issue in itself.