CWE-386 Symbolic Name not Mapping to Correct Object

base

A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.

01

übergeordnete Schwächen

Übergeordnete Klassen, zu denen dies gehört.

02

Schwachstellen (6)

Zugehörige CVEs.

IDSchweregrad ausnutzbar
CVE-2026-31542USmedium5.5—
In the Linux kernel, the following vulnerability has been resolved: x86/platform/uv: Handle deconfigured sockets When a socket is deconfigured, it's mapped to SOCK_EMPTY (0xffff)…
CVE-2023-1637USmedium5.5—
A flaw that boot CPU could be vulnerable for the speculative execution behavior kind of attacks in the Linux kernel X86 CPU Power management options functionality was found in the…
CVE-2026-116486USmedium4.5—
Objenesis before 3.6 contains a type confusion vulnerability that allows code in one class loader to substitute objects into another by exploiting instantiator caching keyed on cla…
CVE-2026-94114US——
Symbolic name not mapping to correct class. BCEL caches attacker-controlled classes under their self-declared names without validating the requested name, allowing subsequent lo…
CVE-2026-53081US——
In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars When regsafe() compares two scalar register…
CVE-2024-3852US——
GetBoundName could return the wrong version of an object when JIT optimizations were applied. This vulnerability affects Firefox < 125, Firefox ESR < 115.10, and Thunderbird < 115.…
03

Quelle

Wo diese Definition veröffentlicht ist.

scry

Schwächen wie diese tauchen in realen, ausnutzbaren Angriffsflächen auf. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan