CVE-2023-31191
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 · uneditedDroneScout ds230 Remote ID receiver from BlueMark Innovations is affected by an information loss vulnerability through traffic injection. An attacker can exploit this vulnerability by injecting, on carefully selected channels, high power spoofed Open Drone ID (ODID) messages which force the DroneScout ds230 Remote ID receiver to drop real Remote ID (RID) information and, instead, generate and transmit JSON encoded MQTT messages containing crafted RID information. Consequently, the MQTT broker, typically operated by a system integrator, will have no access to the drones’ real RID information. This issue affects the adjacent channel suppression algorithm present in DroneScout ds230 firmware from version 20211210-1627 through 20230329-1042.
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 · high confidenceThe DroneScout ds230 firmware contains a flawed adjacent channel suppression algorithm that can be exploited by injecting high-power spoofed Open Drone ID messages on carefully selected channels. This causes the receiver to drop legitimate Remote ID data and instead transmit attacker-controlled RID information via MQTT, resulting in information loss for downstream systems.
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 data>= 20211210-1627, <= 20230329-1042CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/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 DroneScout ds230 firmware versionAccess the device management interface or check the firmware version via the device's administrative console or API endpoint typically found in the system information or diagnostics sectionAffected if The installed firmware version falls within the range >= 20211210-1627 AND <= 20230329-1042
-
Verify if MQTT Remote ID transmission is enabledInspect the device configuration settings for MQTT or Remote ID transmission options, typically found under Wireless Settings, RID Configuration, or Data Export settings in the web interface or config fileAffected if MQTT is enabled and configured to transmit Remote ID data to a broker
-
Confirm Open Drone ID message reception is activeReview the device log files or status indicators that show Open Drone ID channel monitoring activity, usually accessible via the diagnostics or radio status pageAffected if Open Drone ID reception is actively enabled and the device is monitoring adjacent channels
-
Check for unexpected MQTT RID messages in downstream systemsReview MQTT consumer logs or aggregation layer data for Remote ID messages that exhibit sudden changes in signal characteristics or metadata that do not match expected patternsAffected if MQTT messages contain RID data with anomalous signal power levels or unusual channel assignments that indicate spoofing
A user is affected if the DroneScout ds230 firmware version is between 20211210-1627 and 20230329-1042 AND MQTT Remote ID transmission is enabled, allowing injected spoofed Open Drone ID messages to replace legitimate RID data in the MQTT stream.
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 dataUpdate DroneScout ds230 firmware to a version beyond 20230329-1042 when available. Additionally, implement independent RID data validation at the MQTT consumer/aggregation layer to detect and flag spoofed messages.
- 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-31191 — 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-31191 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