FKIE_CVE-2019-13916
Vulnerability from fkie_nvd - Published: 2020-04-13 17:15 - Updated: 2026-06-17 02:17| URL | Tags | ||
|---|---|---|---|
| cve@mitre.org | https://community.cypress.com/thread/53681 | Permissions Required, Vendor Advisory | |
| cve@mitre.org | https://github.com/seemoo-lab/frankenstein/blob/master/doc/CVE_2019_13916.md | Exploit, Third Party Advisory | |
| af854a3a-2127-422b-91ae-364da2661108 | https://community.cypress.com/thread/53681 | Permissions Required, Vendor Advisory | |
| af854a3a-2127-422b-91ae-364da2661108 | https://github.com/seemoo-lab/frankenstein/blob/master/doc/CVE_2019_13916.md | Exploit, Third Party Advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| cypress | wiced_studio | 6.2 | |
| cypress | cyw20735b1 | - | |
| cypress | cyw20819a1 | - |
{
"affected": [
{
"affectedData": [
{
"product": "n/a",
"vendor": "n/a",
"versions": [
{
"status": "affected",
"version": "n/a"
}
]
}
],
"source": "cve@mitre.org"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:cypress:wiced_studio:6.2:*:*:*:*:*:*:*",
"matchCriteriaId": "5E328CCC-A78E-43D3-8E2C-8784932CCB7C",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
},
{
"cpeMatch": [
{
"criteria": "cpe:2.3:h:cypress:cyw20735b1:-:*:*:*:*:*:*:*",
"matchCriteriaId": "F6EBADCA-0C07-4AA0-827D-881CD6FEBE49",
"vulnerable": false
},
{
"criteria": "cpe:2.3:h:cypress:cyw20819a1:-:*:*:*:*:*:*:*",
"matchCriteriaId": "9A994160-E586-4C7F-9082-22518AF475CE",
"vulnerable": false
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "AND"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "An issue was discovered in Cypress (formerly Broadcom) WICED Studio 6.2 CYW20735B1 and CYW20819A1. As a Bluetooth Low Energy (BLE) packet is received, it is copied into a Heap (ThreadX Block) buffer. The buffer allocated in dhmulp_getRxBuffer is four bytes too small to hold the maximum of 255 bytes plus headers. It is possible to corrupt a pointer in the linked list holding the free buffers of the g_mm_BLEDeviceToHostPool Block pool. This pointer can be fully controlled by overflowing with 3 bytes of packet data and the first byte of the packet CRC checksum. The checksum can be freely chosen by adapting the packet data accordingly. An attacker might be able to allocate the overwritten address as a receive buffer resulting in a write-what-where condition. This is fixed in BT SDK2.4 and BT SDK2.45."
},
{
"lang": "es",
"value": "Se detect\u00f3 un problema en Cypress (anteriormente Broadcom) WICED Studio versi\u00f3n 6.2 CYW20735B1 y CYW20819A1. Cuando un paquete Bluetooth Low Energy (BLE) es recibido, es copiado en un b\u00fafer Heap (ThreadX Block). El b\u00fafer asignado en dhmulp_getRxBuffer es cuatro bytes mas peque\u00f1o para contener el m\u00e1ximo de 255 bytes m\u00e1s encabezados. Es posible corromper un puntero en la lista vinculada contenedora de los b\u00faferes libres del grupo Block g_mm_BLEDeviceToHostPool. Este puntero puede ser controlado completamente al desbordar con 3 bytes del paquete de datos y el primer byte de la suma de comprobaciones CRC del paquete. La suma de comprobaciones puede ser elegida libremente al adaptar los datos del paquete en consecuencia. Un atacante podr\u00eda ser capaz de asignar la direcci\u00f3n sobrescrita como un b\u00fafer de recepci\u00f3n, resultando en una condici\u00f3n write-what-where. Esto se corrigi\u00f3 en BT SDK2.4 y BT SDK2.45."
}
],
"id": "CVE-2019-13916",
"lastModified": "2026-06-17T02:17:24.523",
"metrics": {
"cvssMetricV2": [
{
"acInsufInfo": false,
"baseSeverity": "MEDIUM",
"cvssData": {
"accessComplexity": "LOW",
"accessVector": "ADJACENT_NETWORK",
"authentication": "NONE",
"availabilityImpact": "PARTIAL",
"baseScore": 5.8,
"confidentialityImpact": "PARTIAL",
"integrityImpact": "PARTIAL",
"vectorString": "AV:A/AC:L/Au:N/C:P/I:P/A:P",
"version": "2.0"
},
"exploitabilityScore": 6.5,
"impactScore": 6.4,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"source": "nvd@nist.gov",
"type": "Primary",
"userInteractionRequired": false
}
],
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
]
},
"published": "2020-04-13T17:15:10.877",
"references": [
{
"source": "cve@mitre.org",
"tags": [
"Permissions Required",
"Vendor Advisory"
],
"url": "https://community.cypress.com/thread/53681"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/seemoo-lab/frankenstein/blob/master/doc/CVE_2019_13916.md"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Permissions Required",
"Vendor Advisory"
],
"url": "https://community.cypress.com/thread/53681"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/seemoo-lab/frankenstein/blob/master/doc/CVE_2019_13916.md"
}
],
"sourceIdentifier": "cve@mitre.org",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-787"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.