Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2024-0727 medium CVSS 5.5

Vulnerability in cryptography (CVE-2024-0727)

Summary

Vulnerability in cryptography (CVE-2024-0727). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 42.0.2 or later.

Original description

The description as published by the source.

Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL
to crash leading to a potential Denial of Service attack

Impact summary: Applications loading files in the PKCS12 format from untrusted
sources might terminate abruptly.

A file in PKCS12 format can contain certificates and keys and may come from an
untrusted source. The PKCS12 specification allows certain fields to be NULL, but
OpenSSL does not correctly check for this case. This can lead to a NULL pointer
dereference that results in OpenSSL crashing. If an application processes PKCS12
files from an untrusted source using the OpenSSL APIs then that application will
be vulnerable to this issue.

OpenSSL APIs that are vulnerable to this are: PKCS12_parse(),
PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes()
and PKCS12_newpass().

We have also fixed a similar issue in SMIME_write_PKCS7(). However since this
function is related to writing data we do not consider it security significant.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-0727 has been found in cryptography.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: upgrade cryptography to 42.0.2 or later.
If unsure, ask your IT team or search "cryptography CVE-2024-0727" on the vendor's site.

CVE-2024-0727 (cryptography) — CWE-476 / CVSS v3 5.5
Attack vector: local / unauthenticated
Patched: 42.0.2 — 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.

📍 Affected scope

Check the vendor advisory for the affected versions of cryptography.

🔥 Severity

Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 42.0.2.

🛡️ 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'cryptography' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で cryptography を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade cryptography to 42.0.2

    ステージング環境で 42.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip cryptography
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"42.0.2"}]}]
PyPI cryptography
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"42.0.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details