CWE-1273: Device Unlock Credential Sharing | Glexia
CWE-1273 (Device Unlock Credential Sharing) weakness overview with consequences, detection methods, mitigations, related CVEs and MITRE ATT&CK context.
Glexia's Take · Automated analysis
CWE-1273: Device Unlock Credential Sharing
Device Unlock Credential Sharing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Confidentiality,Integrity,Availability,Access Control,Accountability,Authentication,Authorization,Non-Repudiation: Modify Memory,Read Memory,Modify Files or Directories,Read Files or Directories,Modify Application Data,Execute Unauthorized Code or Commands,Gain Privileges or Assume Identity,Bypass Protection Mechanism: Once unlock credentials are compromised, an attacker can use the credentials to unlock the device and gain unauthorized access to the hidden functionalities protected by those credentials.
Developer Pattern
CWE-1273 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Automation confidence
high confidence from CWE-1273, 4.20.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Official CWE Definition
CWE-1273: Device Unlock Credential Sharing
The credentials necessary for unlocking a device are shared across multiple parties and may expose sensitive information.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- This example shows how an attacker can take advantage of compromised credentials. When the credentials of multiple organizations are stored together, exposure to third parties occurs frequently.
Remediation
- Integration: Ensure the unlock credentials are shared with the minimum number of parties and with utmost secrecy. To limit the risk associated with compromised credentials, where possible, the credentials should be part-specific.
- Manufacturing: Ensure the unlock credentials are shared with the minimum number of parties and with utmost secrecy. To limit the risk associated with compromised credentials, where possible, the credentials should be part-specific.
Detection
- Code review
- SAST
- DAST
- Focused regression tests
Mappings
Related CVEs, CWEs, and ATT&CK context
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.