CVE-2019-19195Public exploit

Device crash via truncated L2CAP header

Published Feb 10, 2020 · Updated Aug 5, 2024

Improper L2CAP validation in Microchip BluSDK Smart 6.2 and earlier allows physically proximate attackers to crash ATSAMB11 devices. The BLE stack accepts a one-byte link-layer PDU instead of discarding it, treats that byte as the truncated L2CAP length field, and can overflow a reception buffer when the value is large. Exploitation requires Bluetooth radio proximity and interrupts availability by restarting the device when the default watchdog handles the crash.

CVSS severity6.5
Medium
EPSS probability0.70%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper L2CAP validation in Microchip BluSDK Smart 6.2 and earlier allows physically proximate attackers to crash ATSAMB11 devices. The BLE stack accepts a one-byte link-layer PDU instead of discarding it, treats that byte as the truncated L2CAP length field, and can overflow a reception buffer when the value is large. Exploitation requires Bluetooth radio proximity and interrupts availability by restarting the device when the default watchdog handles the crash.

The record

CVE
CVE-2019-19195
Published
Feb 10, 2020
Updated
Aug 5, 2024
Vendor
Unknown vendor
Product
Unknown product
Classifications
T1499.004
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 10, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

6.1NIST NVDAV:A/AC:L/Au:N/C:N/I:N/A:C
6.5NIST NVDCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

T1499.004Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo