VYPR

CWE-123

Write-what-where Condition

BaseDraftLikelihood: High

Description

Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.

Hierarchy (View 1000)

Parents

Children

none

CVEs mapped to this weakness (65)

page 4 of 4
  • CVE-2025-29943MedJan 16, 2026
    risk 0.30cvss —epss 0.00

    Write what were condition within AMD CPUs may allow an admin-privileged attacker to modify the configuration of the CPU pipeline potentially resulting in the corruption of the stack pointer inside an SEV-SNP guest.

  • CVE-2021-36057LowSep 1, 2021
    risk 0.21cvss 3.3epss 0.01

    XMP Toolkit SDK version 2020.1 (and earlier) is affected by a write-what-where condition vulnerability caused during the application's memory allocation process. This may cause the memory management functions to become mismatched resulting in local application denial of service…

  • CVE-2026-47473HigJul 14, 2026
    risk 0.00cvss 7.4epss 0.00

    NVIDIA TensorRT-LLM contains a vulnerability where an attacker could cause a write-what-where condition. A successful exploit of this vulnerability might lead to data tampering, denial of service, and information disclosure.

  • CVE-2026-45257HigJun 26, 2026
    risk 0.00cvss 7.8epss 0.00

    The KTLS receive path decrypted each record in place, assuming that the mbufs holding received data were anonymous and safe to modify. This assumption does not hold for data placed on a socket by sendfile(2), which can reference file-backed memory directly through non-anonymous…

  • CVE-2024-6563HigJul 8, 2024
    risk 0.00cvss 7.5epss 0.00

    Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in Renesas arm-trusted-firmware allows Local Execution of Code. This vulnerability is associated with program files https://github.Com/renesas-rcar/arm-trusted-firmware/blob/rcar_gen3_v2.5/drive…