← Back
CVE-2024-26130
Vulnerability in cryptography (CVE-2024-26130)
Summary
vulnerability in cryptography (CVE-2024-26130). Risk of unauthorized operations or information disclosure. Exploitable via ``pkcs12.serialize_key_and_certificates``. Mitigation: upgrade to `97d231672763cdb5959a3b191e692a362f1b9e55, 42.0.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-26130** has been found in cryptography.
Attackers can target a specific entry point like ``pkcs12.serialize_key_and_certificates`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade cryptography to **97d231672763cdb5959a3b191e692a362f1b9e55, 42.0.4** or later.
If unsure, ask your IT team or search "cryptography CVE-2024-26130" on the vendor's site.
CVE-2024-26130 (cryptography) — CWE-476 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `pkcs12.serialize_key_and_certificates` / `encryption_algorithm` / `hmac_hash` / `ValueError`
Patched: `97d231672763cdb5959a3b191e692a362f1b9e55, 42.0.4` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-476) exists in cryptography. Attackers reach the vulnerable code path via ``pkcs12.serialize_key_and_certificates`` without authentication.
📍 Affected scope
cryptography — . Attack surface: `pkcs12.serialize_key_and_certificates` / `encryption_algorithm` / `hmac_hash` / `ValueError`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **97d231672763cdb5959a3b191e692a362f1b9e55, 42.0.4**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'cryptography' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'cryptography' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `cryptography` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade cryptography to 97d231672763cdb5959a3b191e692a362f1b9e55, 42.0.4ステージング環境で 97d231672763cdb5959a3b191e692a362f1b9e55, 42.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
cryptography
[{"repo":"https:\/\/github.com\/pyca\/cryptography","type":"GIT","events":[{"introduced":"0"},{"fixed":"97d231672763cdb5959a3b191e692a362f1b9e55"}]},{"type":"ECOSYSTEM","events":[{"introduced":"38.0.0"},{"fixed":"42.0.4"}]}]
References
- advisory https://github.com/pyca/cryptography/security/advisories/GHSA-6vqw-3v5j-54x4
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-26130
- advisory https://github.com/advisories/GHSA-6vqw-3v5j-54x4
- package https://github.com/pyca/cryptography
- patch https://github.com/pyca/cryptography/commit/97d231672763cdb5959a3b191e692a362f1b9e55
- report https://github.com/pyca/cryptography/pull/10423
- web https://github.com/pypa/advisory-database/tree/main/vulns/cryptography/PYSEC-2024-225.yaml