Skip to content
OpenAdvisories

Weakness (CWE)

CWE-123: Write-what-where Condition

Base Draft

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.

How to prevent it (2 mitigations)
  1. Architecture and Design

    Use a language that provides appropriate memory abstractions.

  2. Operation

    Use OS-level preventative functionality integrated after the fact. Not a complete solution.

Source: MITRE CWE-123

5 results · Clear filters · Feed

  • Critical 9.1

    Remotion: arbitrary file write vulnerability

    remotion-dev remotion v4.0.409 was discovered to contain an arbitrary file write vulnerability.

  • Critical 9.8

    A write-what-where condition in p2r3 Bareiron commit 8e4d40 allows unauthenticated attackers to write arbitrary values …

  • Critical 10.0

    llama.cpp allows write-what-where in rpc_server::set_tensor

    llama.cpp provides LLM inference in C/C++. The unsafe `data` pointer member in the `rpc_tensor` structure can cause arbitrary address writing. This vulnerability is fixed in b3561.

  • Critical 9.8

    A heap out-of-bounds write vulnerability exists in the way OpenImageIO v2.3.19.0 processes RLE encoded BMP images. A sp…

  • Critical 9.8

    AUVESY Versiondog

    Some API functions permit by-design writing or copying data into a given buffer. Since the client controls these parameters, an attacker could rewrite the memory in any location of the affected product.