GHSA-jm77-qphf-c4w8 json
pyca/cryptography's wheels include vulnerable OpenSSL
published 3y ago modified 2mo ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi cryptography 41.0.3
Is GHSA-jm77-qphf-c4w8 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | cryptography | >=0.8, <41.0.3 |
41.0.3 |
References
-
github.com
/pyca/cryptography/commit/b22271cf3c3dd8dc8978f8f4b00b5c7060b6538d
web
-
github.com
/pyca/cryptography/commit/bfa4d95f0f356f2d535efd5c775e0fb3efe90ef2
web
-
github.com
/pyca/cryptography/security/advisories/GHSA-jm77-qphf-c4w8
web, advisory
-
github.com
/pyca/cryptography
package
-
openssl.org
/news/secadv/20230714.txt
web
-
openssl.org
/news/secadv/20230719.txt
web
-
openssl.org
/news/secadv/20230731.txt
web
Sources
- GitHub Advisory GHSA-jm77-qphf-c4w8
- Maintainer advisory GHSA-jm77-qphf-c4w8
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of pyca/cryptography published their own advisory on GitHub. Reviewed sources take precedence over it.