CVE-2019-13916

{
  "id": "CVE-2019-13916",
  "cveTags": [],
  "metrics": {
    "cvssMetricV2": [
      {
        "type": "Primary",
        "source": "nvd@nist.gov",
        "cvssData": {
          "version": "2.0",
          "baseScore": 5.8,
          "accessVector": "ADJACENT_NETWORK",
          "vectorString": "AV:A/AC:L/Au:N/C:P/I:P/A:P",
          "authentication": "NONE",
          "integrityImpact": "PARTIAL",
          "accessComplexity": "LOW",
          "availabilityImpact": "PARTIAL",
          "confidentialityImpact": "PARTIAL"
        },
        "acInsufInfo": false,
        "impactScore": 6.4,
        "baseSeverity": "MEDIUM",
        "obtainAllPrivilege": false,
        "exploitabilityScore": 6.5,
        "obtainUserPrivilege": false,
        "obtainOtherPrivilege": false,
        "userInteractionRequired": false
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Primary",
        "source": "nvd@nist.gov",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 8.8,
          "attackVector": "ADJACENT_NETWORK",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 5.9,
        "exploitabilityScore": 2.8
      }
    ]
  },
  "affected": [
    {
      "source": "cve@mitre.org",
      "affectedData": [
        {
          "vendor": "n/a",
          "product": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ]
    }
  ],
  "published": "2020-04-13T17:15:10.877",
  "references": [
    {
      "url": "https://community.cypress.com/thread/53681",
      "tags": [
        "Permissions Required",
        "Vendor Advisory"
      ],
      "source": "cve@mitre.org"
    },
    {
      "url": "https://github.com/seemoo-lab/frankenstein/blob/master/doc/CVE_2019_13916.md",
      "tags": [
        "Exploit",
        "Third Party Advisory"
      ],
      "source": "cve@mitre.org"
    },
    {
      "url": "https://community.cypress.com/thread/53681",
      "tags": [
        "Permissions Required",
        "Vendor Advisory"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    },
    {
      "url": "https://github.com/seemoo-lab/frankenstein/blob/master/doc/CVE_2019_13916.md",
      "tags": [
        "Exploit",
        "Third Party Advisory"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    }
  ],
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "type": "Primary",
      "source": "nvd@nist.gov",
      "description": [
        {
          "lang": "en",
          "value": "CWE-787"
        }
      ]
    }
  ],
  "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ó un problema en Cypress (anteriormente Broadcom) WICED Studio versión 6.2 CYW20735B1 y CYW20819A1. Cuando un paquete Bluetooth Low Energy (BLE) es recibido, es copiado en un búfer Heap (ThreadX Block). El búfer asignado en dhmulp_getRxBuffer es cuatro bytes mas pequeño para contener el máximo de 255 bytes más encabezados. Es posible corromper un puntero en la lista vinculada contenedora de los búferes 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ía ser capaz de asignar la dirección sobrescrita como un búfer de recepción, resultando en una condición write-what-where. Esto se corrigió en BT SDK2.4 y BT SDK2.45."
    }
  ],
  "lastModified": "2026-06-17T02:17:24.523",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:cypress:wiced_studio:6.2:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "5E328CCC-A78E-43D3-8E2C-8784932CCB7C"
            }
          ],
          "operator": "OR"
        },
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:h:cypress:cyw20735b1:-:*:*:*:*:*:*:*",
              "vulnerable": false,
              "matchCriteriaId": "F6EBADCA-0C07-4AA0-827D-881CD6FEBE49"
            },
            {
              "criteria": "cpe:2.3:h:cypress:cyw20819a1:-:*:*:*:*:*:*:*",
              "vulnerable": false,
              "matchCriteriaId": "9A994160-E586-4C7F-9082-22518AF475CE"
            }
          ],
          "operator": "OR"
        }
      ],
      "operator": "AND"
    }
  ],
  "sourceIdentifier": "cve@mitre.org"
}