CVE-2023-28540
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 · uneditedCryptographic issue in Data Modem due to improper authentication during TLS handshake.
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 cryptographic vulnerability exists in Data Modem where improper authentication occurs during the TLS handshake, potentially allowing man-in-the-middle attacks or unauthorized access due to insufficient certificate validation or trust verification.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 installed Qualcomm modem firmware modelCheck the modem firmware version by querying the device or checking system information for one of these models: 315 5g IoT, Aqt1000, Ar8035, Csra6620, Csra6640, Wcn3991, Wcn3998, or Wcn6750Affected if The device is running any version of the listed Qualcomm firmware products
-
Confirm Data Modem component is in useVerify that the TLS communication is handled by the Data Modem component. Check application logs or network configuration to identify if Data Modem processes TLS connectionsAffected if Data Modem component is actively handling TLS communications
-
Inspect TLS certificate validation configurationExamine the modem or host configuration for TLS certificate validation settings. Look for configuration files or registry entries controlling certificate chain verification and trust validationAffected if Certificate validation is disabled, set to permissive, or not properly configured
-
Review trust store configurationCheck the trust store or CA certificate bundle used by the Data Modem for TLS connections. Verify that trusted root certificates are properly installed and not bypassedAffected if Trust store is empty, missing, or certificates are unconditionally trusted
-
Check for certificate validation failures in logsSearch system or application logs for TLS handshake events, certificate validation errors, or warnings related to authentication failures during TLS connectionsAffected if Logs show successful TLS connections despite invalid or missing certificates
A system is affected if it uses any version of the listed Qualcomm firmware products with Data Modem handling TLS connections where certificate validation or trust verification is disabled or misconfigured.
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 dataEnsure proper TLS certificate chain validation, trust store configuration, and authentication verification are implemented correctly in the Data Modem component.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28540 — 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-2023-28540 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