Skip to content
Noroxi
CVE-2018-10903· NVD / CVE Program· CNA redhat

A flaw was found in python-cryptography versions between >=1.9.0 and <2.3.

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.

HighCVSS 7.5 · v3.0—No exploit Fix available
Published
Jul 30, 2018
Updated
Jun 16, 2026
EPSS
3.2% · 88th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.2%

CNA vs NVD score

NVD
7.5
CNA · redhat
7.5
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
cryptographypython-cryptography
redhatopenstack
canonicalubuntu linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux18.04
  • cryptography python-cryptography1.9.0 and later · before 2.3
  • redhat openstack13

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • [UNKNOWN] python-cryptography

    • 2.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12python-cryptographybefore 2.3-12.3-1
openSUSE:Leap 15.3python-cryptography-vectorsbefore 2.9.2-150200.3.3.12.9.2-150200.3.3.1
PyPIcryptographyfrom 1.9 · before 2.32.3
PyPIcryptographyfrom 1.9.0 · before 2.32.3
Red Hat:openstack:13::el7python-cryptographybefore 0:2.1.4-3.el7ost0:2.1.4-3.el7ost
Red Hat:openstack:13::el7python-cryptography-debuginfobefore 0:2.1.4-3.el7ost0:2.1.4-3.el7ost
Red Hat:openstack:13::el7python2-cryptographybefore 0:2.1.4-3.el7ost0:2.1.4-3.el7ost
SUSE:HPE Helion OpenStack 8python-cffibefore 1.11.2-5.11.11.11.2-5.11.1
SUSE:HPE Helion OpenStack 8python-cryptographybefore 2.0.3-3.3.12.0.3-3.3.1
SUSE:HPE Helion OpenStack 8python-cryptographybefore 2.1.4-7.28.22.1.4-7.28.2
SUSE:HPE Helion OpenStack 8python-xattrbefore 0.7.5-6.3.20.7.5-6.3.2
SUSE:Linux Enterprise Module for Basesystem 15python-cryptographybefore 2.1.4-4.3.12.1.4-4.3.1
SUSE:Linux Enterprise Module for Basesystem 15 SP3python-cryptographybefore 2.9.2-150200.13.12.9.2-150200.13.1
SUSE:Linux Enterprise Module for Basesystem 15 SP3python-cryptographybefore 2.9.2-150200.13.12.9.2-150200.13.1
SUSE:Linux Enterprise Server for SAP Applications 12 SP1python-cffibefore 1.11.2-2.19.21.11.2-2.19.2
SUSE:Linux Enterprise Server for SAP Applications 12 SP1python-xattrbefore 0.7.5-3.2.10.7.5-3.2.1
SUSE:OpenStack Cloud 6-LTSSpython-cryptographybefore 2.1.4-3.15.52.1.4-3.15.5

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:python-cryptography2.3-1 · Debian:12Package registry (OSV)
opensuse:python-cryptography2.9.2-150200.13.1 · openSUSE:Leap Micro 5.2Package registry (OSV)
opensuse:python-cryptography-vectors2.9.2-150200.3.3.1 · openSUSE:Leap 15.3Package registry (OSV)
PyPI:cryptography2.3Package registry (OSV)
red hat:python-cryptography0:2.1.4-3.el7ost · Red Hat:openstack:13::el7Package registry (OSV)
red hat:python-cryptography-debuginfo0:2.1.4-3.el7ost · Red Hat:openstack:13::el7Package registry (OSV)
red hat:python2-cryptography0:2.1.4-3.el7ost · Red Hat:openstack:13::el7Package registry (OSV)
suse:python-cffi1.11.2-2.19.2 · SUSE:Linux Enterprise Server for SAP Applications 12 SP1Package registry (OSV)
suse:python-cryptography2.1.4-4.3.1 · SUSE:Linux Enterprise Module for Basesystem 15Package registry (OSV)
suse:python-cryptography2.9.2-150200.13.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3Package registry (OSV)
suse:python-xattr0.7.5-3.2.1 · SUSE:Linux Enterprise Server for SAP Applications 12 SP1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records