Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

GHSA-JM77-QPHF-C4W8

pyca/cryptography's wheels include vulnerable OpenSSL

Overview

Published
1 Aug 2023
Modified
1 Aug 2023
Low GitHub advisory
3 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available
CVSS score Low, no score

Description

pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 0.8-41.0.2 are vulnerable to several security issues. More details about the vulnerabilities themselves can be found in https://www.openssl.org/news/secadv/20230731.txt, https://www.openssl.org/news/secadv/20230719.txt, and https://www.openssl.org/news/secadv/20230714.txt.

If you are building cryptography source ("sdist") then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.

Source: OX vulnerability database

Severity

LOW

No CVSS vector in the source. Severity comes from the advisory.

Affected packages · 3

Packages affected by GHSA-JM77-QPHF-C4W8
EcosystemPackageVulnerableFixed in
PyPI cryptography >=0.8, <41.0.3 41.0.3
Seal PyPI cryptography >=2.9.2+sp0, <2.9.2+sp999>=3.4+sp0, <3.4+sp999>=3.4.8+sp0, <3.4.8+sp999>=35.0.0+sp0, <35.0.0+sp999>=39.0.1+sp0, <39.0.1+sp999+1 more 2.9.2+sp9993.4+sp9993.4.8+sp99935.0.0+sp99939.0.1+sp999
Seal PyPI seal-cryptography >=2.9.2+sp1, <2.9.2+sp999>=3.4+sp1, <3.4+sp999>=3.4.8+sp1, <3.4.8+sp999>=35.0.0+sp1, <35.0.0+sp999>=39.0.1+sp1, <39.0.1+sp999+1 more 2.9.2+sp9993.4+sp9993.4.8+sp99935.0.0+sp99939.0.1+sp999

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.