← Back
CVE-2023-0286
Vulnerability in cryptography (CVE-2023-0286)
Summary
vulnerability in cryptography (CVE-2023-0286). Confidential information can be exposed externally. Exploitable via ``GeneralName``. Mitigation: upgrade to `39.0.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2023-0286** has been found in cryptography.
Attackers can target a specific entry point like ``GeneralName`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade cryptography to **39.0.1** or later.
If unsure, ask your IT team or search "cryptography CVE-2023-0286" on the vendor's site.
CVE-2023-0286 (cryptography) — CWE-843 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `GeneralName` / `ASN1_STRING` / `GENERAL_NAME` / `x400Address`
Patched: `39.0.1` — 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-843) exists in cryptography. Attackers reach the vulnerable code path via ``GeneralName`` without authentication.
📍 Affected scope
cryptography — . Attack surface: `GeneralName` / `ASN1_STRING` / `GENERAL_NAME` / `x400Address`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **39.0.1**.
🛡️ 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 39.0.1ステージング環境で 39.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
cryptography
[{"type":"ECOSYSTEM","events":[{"introduced":"0.8.1"},{"fixed":"39.0.1"}]}]
crates.io
openssl-src
[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"111.25.0"},{"introduced":"300.0.0"},{"fixed":"300.0.12"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2023-0286
- advisory https://rustsec.org/advisories/RUSTSEC-2023-0006.html
- advisory https://github.com/advisories/GHSA-x4qr-2fvf-3mr5
- package https://github.com/pyca/cryptography
- package https://pypi.org/project/cryptography
- package https://crates.io/crates/openssl-src
- web https://github.com/pyca/cryptography/security/advisories/GHSA-x4qr-2fvf-3mr5
- web https://access.redhat.com/security/cve/cve-2023-0286
- web https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-3.6.2-relnotes.txt
- web https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/018_x509.patch.sig
- web https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2c6c9d439b484e1ba9830d8454a34fa4f80fdfe9
- web https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2f7530077e0ef79d98718138716bc51ca0cad658
- web https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fd2af07dc083a350c959147097003a14a5e8ac4d
- web https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003
- web https://security.gentoo.org/glsa/202402-08
- web https://www.openssl.org/news/secadv/20230207.txt