A write-what-where condition in p2r3 Bareiron commit 8e4d40 allows unauthenticated attackers to write arbitrary values t
remotion-dev remotion v4.0.409 was discovered to contain an arbitrary file write vulnerability.
In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb fra
In WibuKey for Windows before version 6.71, an untrusted pointer dereference in the WibuKey2_64.sys kernel driver for 64
iccDEV provides a set of libraries and tools that allow for the interaction, manipulation, and application of ICC color
Local privilege escalation due to improper input validation. The following products are affected: Acronis DeviceLock DLP
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Also unshare DATA/RESPONSE packets when page
In the Linux kernel, the following vulnerability has been resolved: net: skbuff: preserve shared-frag marker during coa
In the Linux kernel, the following vulnerability has been resolved: net: gro: don't merge zcopy skbs skb_gro_receive()
The KTLS receive path decrypted each record in place, assuming that the mbufs holding received data were anonymous and s
NVIDIA TensorRT-LLM contains a vulnerability where an attacker could cause a write-what-where condition. A successful ex
In trusted_mem, there is a possible escalation of privilege due to improper input validation. This could lead to local e
Write what were condition within AMD CPUs may allow an admin-privileged attacker to modify the configuration of the CPU
An improper access control vulnerability exists in Semtech LoRa LR11xxx transceivers running early versions of firmware
Frequently Asked Questions
What is CWE-123?
CWE-123 (CWE-123) is a weakness category in the Common Weakness Enumeration (CWE) system maintained by MITRE. It describes a class of software or hardware vulnerability that can lead to security issues.
How many CVEs are classified as CWE-123?
There are 15 CVE records associated with CWE-123 in our database. Of these, 2 are critical severity, 9 are high severity, and 1 are medium severity.
How can I protect against CWE-123 vulnerabilities?
Protection strategies depend on the specific weakness type. General measures include input validation, secure coding practices, regular security testing, and keeping software up to date. CyberStrike can help by automatically scanning your infrastructure for vulnerabilities related to CWE-123 using AI-powered security agents.
Detect CWE-123 Vulnerabilities
CyberStrike's AI agents automatically detect cwe-123 vulnerabilities across your infrastructure.
Get Started