by @LeSuisse Activity log
- Created automatic suggestion
-
@LeSuisse
removed
13 packages
- python312Packages.django-cryptography
- python313Packages.django-cryptography
- python314Packages.django-cryptography
- python312Packages.mypy-boto3-payment-cryptography
- python313Packages.mypy-boto3-payment-cryptography
- python314Packages.mypy-boto3-payment-cryptography
- python312Packages.mypy-boto3-payment-cryptography-data
- python313Packages.mypy-boto3-payment-cryptography-data
- python314Packages.mypy-boto3-payment-cryptography-data
- python312Packages.types-aiobotocore-payment-cryptography
- python313Packages.types-aiobotocore-payment-cryptography
- python312Packages.types-aiobotocore-payment-cryptography-data
- python313Packages.types-aiobotocore-payment-cryptography-data
-
@LeSuisse
removed
5 maintainers
- @SuperSandro2000
- @centromere
- @mbalatsko
- @fabaff
- @mdaniels5757
- @LeSuisse accepted
- @LeSuisse published on GitHub
cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 46.0.5, the public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve. This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup. Only SECT curves are impacted by this. This vulnerability is fixed in 46.0.5.
References
- https://github.com/pyca/cryptography/commit/0eebb9dbb6343d9bc1d91e5a2482ed4e054a6d8c x_refsource_MISC
- https://github.com/pyca/cryptography/security/advisories/GHSA-r6ph-v2qm-q3c2 x_refsource_CONFIRM
- http://www.openwall.com/lists/oss-security/2026/02/10/4
- https://github.com/pyca/cryptography/security/advisories/GHSA-r6ph-v2qm-q3c2 x_refsource_CONFIRM
- https://github.com/pyca/cryptography/commit/0eebb9dbb6343d9bc1d91e5a2482ed4e054a6d8c x_refsource_MISC
- http://www.openwall.com/lists/oss-security/2026/02/10/4
Affected products
- ==< 46.0.5
Matching in nixpkgs
pkgs.python312Packages.cryptography
Package which provides cryptographic recipes and primitives
pkgs.python313Packages.cryptography
Package which provides cryptographic recipes and primitives
pkgs.python314Packages.cryptography
Package which provides cryptographic recipes and primitives
Package maintainers
Ignored maintainers (2)
-
@SuperSandro2000 Sandro Jäckel <sandro.jaeckel@gmail.com>
-
@mdaniels5757 Michael Daniels <nix@mdaniels.me>