CWEweakness

CWE-1268 Policy Privileges are not Assigned Consistently Between Control and Data Agents

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

Description

The product's hardware-enforced access control for a particular resource improperly accounts for privilege discrepancies between control and write policies.

Common consequences

• Confidentiality, Integrity, Availability, Access Control: Modify Memory, Read Memory, DoS: Crash, Exit, or Restart, Execute Unauthorized Code or Commands, Gain Privileges or Assume Identity, Bypass Protection Mechanism, Read Files or Directories, Reduce Reliability — Resources that include agents in their control policy but not in their write policy could unintentionally allow an untrusted agent to insert itself in the write policy register. Inclusion in the write policy register could allow a malicious or misbehaving agent write access to resources. This action could result in security compromises including leaked information, leaked encryption keys, or modification of device configuration.

Potential mitigations

• [Architecture and Design, Implementation] Access-control-policy definition and programming flow must be sufficiently tested in pre-silicon and post-silicon testing.

Related

Attack pattern · CAPEC (1)

  • CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels attack pattern

Child of · CWE (1)

  • CWE-266 Incorrect Privilege Assignment weakness

Referenced by CAPEC · weakness (1)

  • CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels attack pattern

Referenced by CVE · weakness (1)

  • CVE-2026-5892 Insufficient policy enforcement in PWAs in Google Chrome prior to 147.0.7727.55 allowed a remote attacker who had compromised the renderer… vulnerability