Cyber Resilience

CWE · MITRE source

CWE-843Access of Resource Using Incompatible Type ('Type Confusion')

Abstraction: Base · CVEs in our corpus: 808

The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.

When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties. In languages without memory safety, such as C and C++, type confusion can lead to out-of-bounds memory access. While this weakness is frequently associated with unions when parsing data with many different embedded object types in C, it can be present in any application that can interpret the same variable or memory location in multiple ways. This weakness is not unique to C and C++. For example, errors in PHP applications can be triggered by providing array parameters when scalars are expected, or vice versa. Languages such as Perl, which perform automatic conversion of a variable of one type when it is accessed as if it were another type, can also contain these issues.

Last updated: 04 July 2026 00:28 UTC

Cumulative inbound coverage

How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.

Collective: full · 8 mapping(s) from 2 framework(s): ATT&CK 5 (mostly) · ASVS 5.0 3 (full)

See the full cumulative-coverage rollup →

NIST 800-53 r5 controls that address this weakness (0)AI

Control Title Family Why it addresses this CWE
No NIST controls proposed yet.

MITRE ATT&CK techniques this weakness enables

Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.

Direction: other covers this; this covers other (F/M/P = full / mostly / partial).

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2011-0611 KEV10.08.80.99412011-04-13
CVE-2012-0507 KEV10.09.80.98242012-06-07
CVE-2016-7201 KEV10.08.80.79692016-11-10
CVE-2017-0037 KEV10.08.10.80392017-02-26
CVE-2017-8291 KEV10.07.80.96972017-04-27
CVE-2017-11292 KEV10.08.80.12102017-10-22
CVE-2017-5070 KEV10.08.80.31212017-10-27
CVE-2018-8298 KEV10.07.50.75342018-07-11
CVE-2019-0752 KEV10.07.50.81552019-04-09
CVE-2019-11707 KEV10.08.80.37952019-07-23
CVE-2019-8506 KEV10.08.80.18112019-12-18
CVE-2020-6418 KEV10.08.80.78812020-02-27
CVE-2019-17026 KEV10.08.80.46592020-03-02
CVE-2020-16009 KEV10.08.80.48572020-11-03
CVE-2020-27932 KEV10.07.80.10342020-12-08
CVE-2021-1789 KEV10.08.80.14542021-04-02
CVE-2021-21224 KEV10.08.80.57742021-04-26
CVE-2021-30551 KEV10.08.80.64702021-06-15
CVE-2021-30563 KEV10.08.80.08932021-08-03
CVE-2021-30869 KEV10.07.80.04152021-08-24
CVE-2022-1096 KEV10.08.80.24242022-07-23
CVE-2022-1364 KEV10.08.80.13722022-07-26
CVE-2022-41033 KEV10.07.80.01782022-10-11
CVE-2022-3723 KEV10.08.80.06752022-11-01
CVE-2022-4262 KEV10.08.80.16112022-12-02