CWE-1351: Improper Handling of Hardware Behavior in Exceptionally Cold Environments
Weakness ID: 1351
Vulnerability Mapping:ALLOWEDThis CWE ID could be used to map to real-world vulnerabilities in limited situations requiring careful review
(with careful review of mapping notes)
Abstraction:
BaseBase - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
View customized information:
Shows the description and diagram, platforms, mitigations, consequences, relationships, memberships, and content history.For users who are interested in more notional aspects of a weakness. Example: educators, technical writers, and project/program managers.For users who are concerned with the practical application and details about the nature of a weakness and how to prevent it from happening. Example: tool developers, security researchers, pen-testers, incident response analysts.For users who are mapping an issue to CWE/CAPEC IDs, i.e., finding the most appropriate CWE for a specific issue (e.g., a CVE record). Example: tool developers, security researchers.For users who wish to see all available information for the CWE/CAPEC entry.For users who want to customize what details are displayed.
×
Edit Custom Filter
More information is available — Please edit the custom filter or select a different filter.
Description
The hardware device, or the firmware running on it, is
missing or has incorrect protection mechanisms to maintain
goals of security primitives when the device is cooled below
standard operating temperatures.
Common Consequences
This table specifies different individual consequences
associated with the weakness. The Scope identifies the application security area that is
violated, while the Impact describes the negative technical impact that arises if an
adversary succeeds in exploiting this weakness. The Likelihood provides information about
how likely the specific consequence is expected to be seen relative to the other
consequences in the list. For example, there may be high likelihood that a weakness will be
exploited to achieve a certain impact, but a low likelihood that it will be exploited to
achieve a different impact.
Impact
Details
Varies by Context; Unexpected State
Scope: Integrity, AuthenticationLikelihood: Low
This may result in a weakness when the
starting state of the volatile memory is being
relied upon for a security decision. Consequences
of this weakness are highly contextual.
Potential Mitigations
Phase(s)
Mitigation
Architecture and Design
The system should account for security primitive behavior when cooled outside standard temperatures.
Relationships
This table shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOf and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition,
relationships such as PeerOf, Overlaps, and CanAlsoBe are defined to show similar weaknesses that the user
may want to explore.
Relevant to the view "Complete Weakness Hierarchy" (View-1000)
Nature
Type
ID
Name
ChildOf
Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource.
The different Modes of Introduction provide information
about how and when this
weakness may be introduced. The Phase identifies a point in the life cycle at which
introduction
may occur, while the Note provides a typical scenario related to introduction during the
given
phase.
Phase(s)
Note
Architecture and Design
The hardware designer may improperly anticipate
hardware behavior when exposed to exceptionally cold
conditions. As a result, they may introduce a weakness by not
accounting for the modified behavior of critical components
when in extreme environments.
Implementation
Applicable Platforms
This listing shows possible areas for which the given
weakness could appear. These
may be for specific named Languages, Operating Systems, Architectures, Paradigms,
Technologies,
or a class of such platforms. The platform is listed along with how frequently the given
weakness appears for that instance.
Type
Applicable Platforms
Notes
Languages
Class: Not Language-Specific
(Undetermined Prevalence)
Operating Systems
Class: Not OS-Specific
(Undetermined Prevalence)
Architectures
Class: Embedded
(Undetermined Prevalence)
Class: Microcomputer
(Undetermined Prevalence)
Technologies
Class: System on Chip
(Undetermined Prevalence)
Demonstrative Examples
Example 1
Consider a product in which power loss
does not clear or reset any volatile state when cooled
below standard operating temperatures. For example, a
Physical Unclonable Function (PUF) may be supplied as
a security primitive to improve confidentiality,
authenticity, and integrity guarantees.
(bad code)
Example Language: Algorithm
When the PUF is paired with DRAM, SRAM, or
another temperature-sensitive entropy source,
the system designer may introduce a weakness by
failing to account for the chosen entropy
source's behavior at exceptionally low
temperatures.
In the case of DRAM and SRAM, when power is cycled
at low temperatures, the device will not contain the
bitwise biasing caused by inconsistencies in
manufacturing and will instead contain the data from
previous boot. Should the PUF primitive be used in a
cryptographic construction which does not account
for full adversary control of PUF seed data,
weakness would arise.
Weakness Ordinalities
Ordinality
Description
Primary
(where the weakness exists independent of other weaknesses)
Memberships
This MemberOf Relationships table shows additional CWE Categories and Views that
reference this weakness as a member. This information is often useful in understanding where a
weakness fits within the context of external information sources.
Nature
Type
ID
Name
MemberOf
Grouping - a CWE entry that contains a set of other entries that share a common characteristic.
Comprehensive Categorization: Improper Check or Handling of Exceptional Conditions
Vulnerability Mapping Notes
Usage
ALLOWED-WITH-REVIEW
(this CWE ID could be used to map to real-world vulnerabilities in limited situations requiring careful review)
Reason
Acceptable-Use
Rationale
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Comments
This weakness does not cover "Cold Boot
Attacks" wherein RAM or other external storage is
super-cooled and read externally by an
attacker.
Carefully read both the name and description to ensure
that this mapping is an appropriate fit. Do not try to
'force' a mapping to a lower-level Base/Variant simply
to comply with this preferred level of abstraction.
Yuan Cao, Yunyi Guo, Benyu Liu, Wei Ge, Min Zhu and Chip-Hong Chang. "A Fully Digital Physical Unclonable Function Based Temperature Sensor for Secure Remote Sensing". 2018-10-11.
<https://ieeexplore.ieee.org/abstract/document/8487347/>.
[REF-1183]
Urbi Chatterjee, Soumi Chatterjee, Debdeep Mukhopadhyay and Rajat Subhra Chakraborty. "Machine Learning Assisted PUF Calibration for Trustworthy Proof of Sensor Data in IoT". 2020-06.
<https://dl.acm.org/doi/abs/10.1145/3393628>.
(URL validated: 2023-04-07)