CVE-2023-28561
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 · uneditedMemory corruption in QESL while processing payload from external ESL device to firmware.
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 confidenceMemory corruption vulnerability in QESL (electronic shelf label management software) allows remote attackers to corrupt memory by sending specially crafted payloads from external ESL devices to the firmware. The lack of proper bounds checking or input validation when processing incoming data from connected ESL devices enables arbitrary memory write conditions, potentially leading to code execution.
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 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 hardware platformCheck system documentation, device inventory, or run 'lspci' or 'cat /proc/cpuinfo' to identify if the system uses Qualcomm Qcn7606 chipset or baseband processorAffected if Hardware platform is confirmed to be Qualcomm Qcn7606
-
Locate QESL serviceSearch for processes related to QESL or electronic shelf label management using commands like 'ps aux | grep -i esl' or 'ps aux | grep -i qesl' if shell access is availableAffected if QESL or ESL management process is found running on the system
-
Check firmware versionIf accessible, examine firmware version information via '/proc/version', bootloader output, or vendor management interface for the Qcn7606 baseband firmwareAffected if Firmware version string shows Qcn7606 and cannot be determined to be patched (vendor advisory states all versions affected)
-
Inspect ESL device connectivityReview network configuration, firewall rules, or VLAN segmentation to determine how ESL devices connect to the QESL management systemAffected if ESL devices are permitted to communicate directly with the QESL server without strict network isolation or input validation at boundary
You are affected if your system runs QESL on Qualcomm Qcn7606 firmware with ESL devices able to send unsolicited data to the management platform.
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 vendor-supplied firmware updates for QESL and ESL devices; if no patch available, isolate ESL device networks from untrusted segments and implement strict input validation at network boundaries.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28561 — 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-28561 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