2092
Abstraction : Base
Description
The product does not properly provide a capability for the product administrator to remove
sensitive data at the time the product is decommissioned. A scrubbing capability could be missing,
insufficient, or incorrect.
Extended Description
When a product is decommissioned - i.e., taken out of service - best practices or regulatory
requirements may require the administrator to remove or overwrite sensitive data first, i.e.
"scrubbing." Improper scrubbing of sensitive data from a decommissioned device leaves that data
vulnerable to acquisition by a malicious actor. Sensitive data may include, but is not limited to,
device/manufacturer proprietary information, user/device credentials, network configurations, and
other forms of sensitive data.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr 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 may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 404 Improper Resource Shutdown or Release 980
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Operating_System : Not OS-Specific (Prevalence = Undetermined)
Architecture : Not Architecture-Specific (Prevalence = Undetermined)
Technology : Not Technology-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Confidentiality Read Memory
Potential Mitigations
Phase: Architecture and Design
Functionality to completely scrub data from a product at the conclusion of its lifecycle should be
part of the design phase. Trying to add this function on top of an existing architecture could lead
to incomplete removal of sensitive information/data.
Phase: Policy
The manufacturer should describe the location(s) where sensitive data is stored and the
policies and procedures for its removal. This information may be conveyed, for example, in an
Administrators Guide or a Statement of Volatility.
Phase: Implementation
If the capability to wipe sensitive data isn't built-in, the manufacturer may need to provide a utility
to scrub sensitive data from storage if that data is located in a place which is non-accessible by
the administrator. One example of this could be when sensitive data is stored on an EEPROM for
which there is no user/admin interface provided by the system.
MemberOf Relationships
CWE Version 4.14
CWE-1267: Policy Uses Obsolete Encoding
CWE-1267: Policy Uses Obsolete Encoding