CWEweakness

CWE-1267 Policy Uses Obsolete Encoding

Official page ↗
Abstraction
Base
Structure
Simple
Status
Draft
Languages
Not Language-Specific
CWE version
5.0

Description

The product uses an encoding mechanism that is no longer trusted, i.e., an obsolete encoding, to implement access controls.

Common consequences

• Confidentiality, Integrity, Availability, Access Control: Modify Memory, Read Memory, Modify Files or Directories, Read Files or Directories, DoS: Resource Consumption (Other), Execute Unauthorized Code or Commands, Gain Privileges or Assume Identity, Bypass Protection Mechanism, Reduce Reliability

Potential mitigations

• [Architecture and Design, Implementation] Security Token Decoders should be reviewed for design inconsistency and common weaknesses. Access and programming flows should be tested in both pre-silicon and post-silicon testing.

Related

Attack pattern · CAPEC (2)

  • CAPEC-121 Exploit Non-Production Interfaces attack pattern
  • CAPEC-681 Exploitation of Improperly Controlled Hardware Security Identifiers attack pattern

Child of · CWE (1)

  • CWE-284 Improper Access Control weakness

Referenced by CAPEC · weakness (2)

  • CAPEC-121 Exploit Non-Production Interfaces attack pattern
  • CAPEC-681 Exploitation of Improperly Controlled Hardware Security Identifiers attack pattern