CVE-2023-28543
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 · uneditedA malformed DLC can trigger Memory Corruption in SNPE library due to out of bounds read, such as by loading an untrusted model (e.g. from a remote source).
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 malformed DLC (Deep Learning Container) file can trigger memory corruption in Qualcomm's SNPE (Snapdragon Neural Processing Engine) library through an out-of-bounds read vulnerability. The vulnerability is triggered when the SNPE library loads an untrusted or unverified model, allowing an attacker to cause memory corruption via a specially crafted DLC file.
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 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 SoC or processor model in useCheck the device's system-on-chip (SoC) information through /proc/cpuinfo, system settings, or firmware binaries to determine the exact Qualcomm processor modelAffected if The processor is a Qualcomm Sd855, Sd845, Qcs605, or Qcs405 (any version)
-
Determine if SNPE library is presentSearch for the presence of the Snapdragon Neural Processing Engine (SNPE) library files (typically named libsnpe*.so or similar) in the firmware or application runtime environmentAffected if The SNPE library is installed or bundled in the firmware
-
Verify DLC model loading functionalityInspect application logs, system traces, or code that invokes the SNPE API to determine if the application loads DLC model files at runtimeAffected if The application or service loads DLC files using the SNPE library
-
Assess DLC file source trustReview where DLC model files originate (local storage, remote download, third-party sources) and whether they undergo integrity or signature verification before loadingAffected if DLC models are loaded from untrusted, unverified, or remote sources without validation checks
The environment is affected if the device runs on a Qualcomm Sd855, Sd845, Qcs605, or Qcs405 firmware and loads DLC models from untrusted or unverified sources into the SNPE library.
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 dataAvoid loading DLC models from untrusted or unverified sources; implement strict validation and verification of model files before passing them to the SNPE library. Consider digital signing and integrity checks for models loaded from remote sources.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28543 — 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-28543 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