CWE-1419
Incorrect Initialization of Resource
Extended description
This can have security implications when the associated resource is expected to have certain properties or values. Examples include a variable that determines whether a user has been authenticated or not, or a register or fuse value that determines the security state of the product. For software, this weakness can frequently occur when implicit initialization is used, meaning the resource is not explicitly set to a specific value. For example, in C, memory is not necessarily cleared when it is allocated on the stack, and many scripting languages use a default empty, null value, or zero value when a variable is not explicitly initialized. For hardware, this weakness frequently appears with reset values and fuses. After a product reset, hardware may initialize registers incorrectly. During different phases of a product lifecycle, fuses may be set to incorrect values. Even if fuses are set to correct values, the lines to the fuse could be broken or there might be hardware on the fuse line that alters the fuse value to be incorrect.
Common consequences3
- ConfidentialityRead MemoryRead Application DataUnexpected State
- AuthorizationIntegrityGain Privileges or Assume Identity
- OtherVaries by Context
The technical impact can vary widely based on how the resource is used in the product, and whether its contents affect security decisions.
Potential mitigations4
- Implementation
Choose the safest-possible initialization for security-related resources.
- Implementation
Ensure that each resource (whether variable, memory buffer, register, etc.) is fully initialized.
- Implementation
Pay close attention to complex conditionals or reset sources that affect initialization, since some paths might not perform the initialization.
- Architecture and Design
Ensure that the design and architecture clearly identify what the initialization should be, and that the initialization does not have security implications.
Relationships1
- ChildOfCWE-665
CVEs referencing this CWE9
| CVE | Description | Severity | EPSS | Flags | Modified |
|---|---|---|---|---|---|
| CVE-2025-53800 | No cwe for this issue in Microsoft Graphics Component allows an authorized attacker to elevate privileges locally. | HIGH7.8 | 0.46%p36 | 2026-02-26 | |
| CVE-2026-21913 | An Incorrect Initialization of Resource vulnerability in the Internal Device Manager (IDM) of Juniper Networks Junos OS on EX4000 models allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). On EX4000 models with 48 ports (EX4000-48T, EX4000-48P, EX4000-48MP) a high volume of traffic destined to the device will cause an FXPC crash and restart, which leads to a complete service outage until the device has automatically restarted. The following reboot reason can be seen in the output of 'show chassis routing-engine' and as a log message: reason=0x4000002 reason_string=0x4000002:watchdog + panic with core dump This issue affects Junos OS on EX4000-48T, EX4000-48P and EX4000-48MP: * 24.4 versions before 24.4R2, * 25.2 versions before 25.2R1-S2, 25.2R2. This issue does not affect versions before 24.4R1 as the first Junos OS version for the EX4000 models was 24.4R1. | HIGH7.5 | 0.38%p29 | 2026-01-23 | |
| CVE-2026-0109 | In dhd_tcpdata_info_get of dhd_ip.c, there is a possible Denial of Service due to a precondition check failure. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. | HIGH7.5 | 0.29%p20 | 2026-03-11 | |
| CVE-2024-0103 | NVIDIA Triton Inference Server for Linux contains a vulnerability where a user may cause an incorrect Initialization of resource by network issue. A successful exploit of this vulnerability may lead to information disclosure. | MEDIUM6.5 | 0.28%p19 | 2025-09-26 | |
| CVE-2023-5078 | A vulnerability was reported in some ThinkPad BIOS that could allow a physical or local attacker with elevated privileges to tamper with BIOS firmware. | MEDIUM6.7 | 0.22%p12 | 2024-11-21 | |
| CVE-2023-45085 | An issue exists in SoftIron HyperCloud where compute nodes may come online immediately without following the correct initialization process. In this instance, workloads may be scheduled on these nodes and deploy to a failed or erroneous state, which impacts the availability of these workloads that may be deployed during this time window. This issue impacts HyperCloud versions from 2.0.0 to before 2.0.3. | LOW3.3 | 0.21%p12 | 2024-11-21 | |
| CVE-2026-33773 | An Incorrect Initialization of Resource vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on specific EX Series and QFX Series device allows an unauthenticated, network-based attacker to cause an integrity impact to downstream networks. When the same family inet or inet6 filter is applied on an IRB interface and on a physical interface as egress filter on EX4100, EX4400, EX4650 and QFX5120 devices, only one of the two filters will be applied, which can lead to traffic being sent out one of these interfaces which should have been blocked. This issue affects Junos OS on EX Series and QFX Series: * 23.4 version 23.4R2-S6, * 24.2 version 24.2R2-S3. No other Junos OS versions are affected. | MEDIUM5.8 | 0.20%p10 | 2026-04-17 | |
| CVE-2024-57375 | Andamiro Pump It Up 20th Anniversary (aka Double X or XX/2019) 1.00.0-2.08.3 allows a physically proximate attacker to cause a denial of service (application crash) via certain deselect actions. | LOW2.4 | 0.18%p8 | 2026-04-15 | |
| CVE-2025-24495 | Incorrect initialization of resource in the branch prediction unit for some Intel(R) Core™ Ultra Processors may allow an authenticated user to potentially enable information disclosure via local access. | MEDIUM5.6 | 0.16%p6 | 2026-04-15 |