CVE-2018-10903

Description

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.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.33%
Vendor Advisory redhat.com Vendor Advisory ubuntu.com
Affected: [UNKNOWN] python-cryptography
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2018-10903?
CVE-2018-10903 has been scored as a high severity vulnerability.
How to fix CVE-2018-10903?
To fix CVE-2018-10903, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-10903 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2018-10903 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2018-10903?
CVE-2018-10903 affects [UNKNOWN] python-cryptography.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.