Détail du CWE-1419

CWE-1419

Incorrect Initialization of Resource
Incomplete
2023-10-26
00h00 +00:00
2024-07-16
00h00 +00:00
CWE Mitre.org
Notifications pour un CWE
Restez informé de toutes modifications pour un CWE spécifique.
Gestion des notifications

Nom: Incorrect Initialization of Resource

The product attempts to initialize a resource but does not correctly do so, which might leave the resource in an unexpected, incorrect, or insecure state when it is accessed.

Description du CWE

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.

Informations générales

Modes d'introduction

Implementation
Manufacturing
Installation
System Configuration
Operation

Plateformes applicables

Langue

Class: Not Language-Specific (Undetermined)

Systèmes d’exploitation

Class: Not OS-Specific (Undetermined)

Architectures

Class: Not Architecture-Specific (Undetermined)

Technologies

Class: Not Technology-Specific (Undetermined)

Conséquences courantes

Portée Impact Probabilité
ConfidentialityRead Memory, Read Application Data, Unexpected StateUnknown
Authorization
Integrity		Gain Privileges or Assume Identity
OtherVaries by Context

Note: The technical impact can vary widely based on how the resource is used in the product, and whether its contents affect security decisions.

Exemples observés

Références Description

CVE-2020-27211

Chain: microcontroller system-on-chip uses a register value stored in flash to set product protection state on the memory bus and does not contain protection against fault injection (CWE-1319) which leads to an incorrect initialization of the memory bus (CWE-1419) causing the product to be in an unprotected state.

CVE-2023-25815

chain: a change in an underlying package causes the gettext function to use implicit initialization with a hard-coded path (CWE-1419) under the user-writable C:\ drive, introducing an untrusted search path element (CWE-427) that enables spoofing of messages.

CVE-2022-43468

WordPress module sets internal variables based on external inputs, allowing false reporting of the number of views

CVE-2022-36349

insecure default variable initialization in BIOS firmware for a hardware board allows DoS

CVE-2015-7763

distributed filesystem only initializes part of the variable-length padding for a packet, allowing attackers to read sensitive information from previously-sent packets in the same memory location

Mesures d’atténuation potentielles

Phases : Implementation
Choose the safest-possible initialization for security-related resources.
Phases : Implementation
Ensure that each resource (whether variable, memory buffer, register, etc.) is fully initialized.
Phases : Implementation
Pay close attention to complex conditionals or reset sources that affect initialization, since some paths might not perform the initialization.
Phases : 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.

Notes de cartographie des vulnérabilités

Justification : This CWE entry is a Class and might have Base-level children that would be more appropriate
Commentaire : Examine children of this entry to see if there is a better fit

Références

REF-1437

acct_wrapper.sv
https://github.com/HACK-EVENT/hackatdac21/blob/65d0ffdab7426da4509c98d62e163bcce642f651/piton/design/chip/tile/ariane/src/acct/acct_wrapper.sv#L39

REF-1438

Bad Code acct_wrapper.sv
https://github.com/HACK-EVENT/hackatdac21/blob/65d0ffdab7426da4509c98d62e163bcce642f651/piton/design/chip/tile/ariane/src/acct/acct_wrapper.sv#L79C1-L86C16

REF-1439

Good Code acct_wrapper.sv
https://github.com/HACK-EVENT/hackatdac21/blob/062de4f25002d2dcbdb0a82af36b80a517592612/piton/design/chip/tile/ariane/src/acct/acct_wrapper.sv#L84

Soumission

Nom Organisation Date Date de publication Version
CWE Content Team MITRE 2023-10-11 +00:00 2023-10-26 +00:00 4.13

Modifications

Nom Organisation Date Commentaire
CWE Content Team MITRE 2024-07-16 +00:00 updated Demonstrative_Examples, References