CVE-2024-23357
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTransient DOS while importing a PKCS#8-encoded RSA key with zero bytes modulus.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA transient denial of service vulnerability exists in PKCS#8-encoded RSA key import functionality. When importing an RSA key with a zero bytes modulus (corrupted or malformed key), the library fails to properly validate the key structure, causing a service disruption during the import process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the deployed firmwareCheck the system information or bootloader to determine if the device runs any of the following Qualcomm firmware variants: Apq8017, Apq8037, Aqt1000, Ar8035, Csra6620, Csra6640, Fastconnect 6200, or Fastconnect 6700. Use commands like 'cat /proc/cpuinfo', 'dmidecode', or check the kernel boot logs for firmware identifiers.Affected if The device is running any of the listed Qualcomm firmware variants.
-
Locate the cryptographic library handling PKCS#8 importIdentify the cryptographic library in use on the firmware. Check for shared object files related to PKCS#8 parsing, typically found in /lib, /usr/lib, or vendor-specific paths. Look for libraries that handle RSA key import such as OpenSSL, mbed TLS, or vendor-specific crypto libraries.Affected if A cryptographic library that processes PKCS#8-encoded keys is present on the system.
-
Verify RSA key import capabilityReview the application configuration or code to determine if PKCS#8 RSA key import functionality is actively used. Check for features that accept PEM or DER-encoded private keys, particularly those using the PKCS#8 format (often begins with '-----BEGIN PRIVATE KEY-----' or contains ASN.1 structure with identifier 1.2.840.113549.1.1.1).Affected if Applications or services on the device are configured to import or process PKCS#8-encoded RSA private keys.
-
Check for key import error handlingIf PKCS#8 RSA key import is in use, examine whether the current library implementation includes explicit validation for zero-length or zero-value RSA modulus (n) during key parsing. This may require reviewing library source code or release notes for the specific cryptographic library version in use.Affected if The cryptographic library lacks explicit validation rejecting RSA keys with zero modulus, and the device imports PKCS#8-encoded RSA keys.
The device is affected if it runs any of the listed Qualcomm firmware variants and uses a cryptographic library that processes PKCS#8-encoded RSA keys without rejecting keys with zero modulus.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the security patch from the library vendor to add proper validation rejecting RSA keys with zero modulus during PKCS#8 import, or upgrade to a patched version of the affected cryptographic library.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23357 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data