python-cryptography: GCM tag forgery via truncated tag in finalize_with_tag API
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| [UNKNOWN] | python-cryptography | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenStack Platform 13.0 (Queens) | |||
| python-cryptography-0:2.1.4-3.el7ost | cpe:/a:redhat:openstack:13::el7 | RHSA-2018:3600 | 2018-11-13T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-0030 | A flaw was found in python-cryptography versions between >=1.9.0 and <2.3. The finalize_with_tag API did not enforce a minimum tag length. If a user did not validate the input length prior to passing it to finalize_with_tag an attacker could craft an invalid payload with a shortened tag (e.g. 1 byte) such that they would have a 1 in 256 chance of passing the MAC check. GCM tag forgeries can cause key leakage. |
Github GHSA |
GHSA-fcf9-3qw3-gxmj | PyCA Cryptography vulnerable to GCM tag forgery |
Ubuntu USN |
USN-3720-1 | python-cryptography vulnerability |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 3.2% (3.196% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.