CWE-1277: Firmware Not Updateable
The product's firmware cannot be updated, which leaves persistent weaknesses with no means of patching them.
The inability to patch the product's firmware means that any weaknesses therein cannot be mitigated through an update. This leaves the system/device open to potential exploitation of the inherent weaknesses present. External protective measures and mitigations can be employed to aid in preventing malicious behavior, but the root weakness cannot be corrected.
The table(s) below 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 and CanAlsoBe are defined to show similar weaknesses that the user may want to explore.
Relevant to the view "Research Concepts" (CWE-1000)
Relevant to the view "Hardware Design" (CWE-1194)
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.
The listings below show 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.
Class: Language-Independent (Undetermined Prevalence)
Class: OS-Independent (Undetermined Prevalence)
Class: Architecture-Independent (Undetermined Prevalence)
Class: Technology-Independent (Undetermined Prevalence)
The table below 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.
An employee’s mobile device is decommissioned due to end of life but sensitive user information, network certificates, and encryption keys are left in device memory/storage.
Example Language: Other
This device is obtained by a malicious individual; either through re-seller or nefarious means. System forensics (e.g. chip decapping) is used to reveal system memory and storage data. Examination of these leads to acquisition of critical and/or sensitive data which can be used to bypass access control, impersonate individuals, or otherwise access potentially proprietary information.
Example Language: Other
Device is scrubbed of sensitive/critical information prior to decommissioning (e.g. resell or disposal). Once obtained by another individual, they are unable to extract any critical or sensitive data since it is not present on the device.
This entry is still under development and will continue to see updates and content improvements.
More information is available — Please select a different filter.