---
title: "CWE-1262: Improper Access Control for Register Interface"
url: https://radicalnotion.ai/cwe/cwe-1262
type: cwe
description: "The product uses memory-mapped I/O registers that act as an interface to hardware functionality from software, but there is improper access control to those registers."
updated: 2026-11-10
source: RadicalNotion.AI
license: CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/)
---

# CWE-1262: Improper Access Control for Register Interface

- **Abstraction:** Base
- **Structure:** Simple
- **Status:** Stable
- **CVEs with this as primary weakness:** 11
- **Of those, in CISA KEV:** 0
- **New in 2026:** 4
- **CWE catalog version:** 4.21

## Description

The product uses memory-mapped I/O registers that act as an interface to hardware functionality from software, but there is improper access control to those registers.

Software commonly accesses peripherals in a System-on-Chip (SoC) or other device through a memory-mapped register interface. Malicious software could tamper with any security-critical hardware data that is accessible directly or indirectly through the register interface, which could lead to a loss of confidentiality and integrity.

## Modes of introduction

| Phase | Note |
| --- | --- |
| Architecture and Design | This weakness may be exploited if the register interface design does not adequately protect hardware assets from software. |
| Implementation | Mis-implementation of access control policies may inadvertently allow access to hardware assets through the register interface. |

## Common consequences

| Scope | Impact | Note |
| --- | --- | --- |
| Confidentiality, Integrity | Read Memory, Read Application Data, Modify Memory, Modify Application Data, Gain Privileges or Assume Identity, Bypass Protection Mechanism, Unexpected State, Alter Execution Logic | Confidentiality of hardware assets may be violated if the protected information can be read out by software through the register interface. Registers storing security state, settings, other security-critical data may be corruptible by software without correctly implemented protections. |

## Potential mitigations

### Architecture and Design

Design proper policies for hardware register access from software.

### Implementation

Ensure that access control policies for register access are implemented in accordance with the specified design.

## Detection methods

### Manual Analysis

This is applicable in the Architecture phase before implementation started. Make sure access policy is specified for the entire memory map. Manual analysis may not ensure the implementation is correct.

Effectiveness: Moderate

### Manual Analysis

Registers controlling hardware should have access control implemented. This access control may be checked manually for correct implementation. Items to check consist of how are trusted parties set, how are trusted parties verified, how are accesses verified, etc. Effectiveness of a manual analysis will vary depending upon how complicated the interface is constructed.

Effectiveness: Moderate

### Simulation / Emulation

Functional simulation is applicable during the Implementation Phase. Testcases must be created and executed for memory mapped registers to verify adherence to the access control policy. This method can be effective, since functional verification needs to be performed on the design, and verification for this weakness will be included. There can be difficulty covering the entire memory space during the test.

Effectiveness: Moderate

### Formal Verification

Formal verification is applicable during the Implementation phase. Assertions need to be created in order to capture illegal register access scenarios and prove that they cannot occur. Formal methods are exhaustive and can be very effective, but creating the cases for large designs may be complex and difficult.

Effectiveness: High

### Automated Analysis

Information flow tracking can be applicable during the Implementation phase. Security sensitive data (assets) - for example, as stored in registers - is automatically tracked over time through the design to verify the data doesn't reach illegal destinations that violate the access policies for the memory map. This method can be very effective when used together with simulation and emulation, since detecting violations doesn't rely on specific scenarios or data values. This method does rely on simulation and emulation, so testcases must exist in order to use this method.

Effectiveness: High

### Architecture or Design Review

Manual documentation review of the system memory map, register specification, and permissions associated with accessing security-relevant functionality exposed via memory-mapped registers.

Effectiveness: Moderate

### Fuzzing

Perform penetration testing (either manual or semi-automated with fuzzing) to verify that access control mechanisms such as the memory protection units or on-chip bus firewall settings adequately protect critical hardware registers from software access.

Effectiveness: Moderate

## Demonstrative examples

### Example 1

The register interface provides software access to hardware functionality. This functionality is an attack surface. This attack surface may be used to run untrusted code on the system through the register interface. As an example, cryptographic accelerators require a mechanism for software to select modes of operation and to provide plaintext or ciphertext data to be encrypted or decrypted as well as other functions. This functionality is commonly provided through registers.

### Example 2

The example code is taken from the Control/Status Register (CSR) module inside the processor core of the HACK@DAC'19 buggy CVA6 SoC \[REF-1340\]. In RISC-V ISA \[REF-1341\], the CSR file contains different sets of registers with different privilege levels, e.g., user mode (U), supervisor mode (S), hypervisor mode (H), machine mode (M), and debug mode (D), with different read-write policies, read-only (RO) and read-write (RW). For example, machine mode, which is the highest privilege mode in a RISC-V system, registers should not be accessible in user, supervisor, or hypervisor modes.

Bad code:

```systemverilog
if (csr_we || csr_read) begin
    if ((riscv::priv_lvl_t'(priv_lvl_o & csr_addr.csr_decode.priv_lvl) != csr_addr.csr_decode.priv_lvl) && !(csr_addr.address==riscv::CSR_MEPC)) begin
        csr_exception_o.cause = riscv::ILLEGAL_INSTR;
        csr_exception_o.valid = 1'b1;
    end
    // check access to debug mode only CSRs
    if (csr_addr_i[11:4] == 8'h7b && !debug_mode_q) begin
        csr_exception_o.cause = riscv::ILLEGAL_INSTR;
        csr_exception_o.valid = 1'b1;
    end
end
```

Good code:

```systemverilog
if (csr_we || csr_read) begin
    if ((riscv::priv_lvl_t'(priv_lvl_o & csr_addr.csr_decode.priv_lvl) != csr_addr.csr_decode.priv_lvl)) begin
        csr_exception_o.cause = riscv::ILLEGAL_INSTR;
        csr_exception_o.valid = 1'b1;
    end
    // check access to debug mode only CSRs
    if (csr_addr_i[11:4] == 8'h7b && !debug_mode_q) begin
        csr_exception_o.cause = riscv::ILLEGAL_INSTR;
        csr_exception_o.valid = 1'b1;
    end
end
```

## Observed examples

| CVE | Description |
| --- | --- |
| CVE-2014-2915 | virtualization product does not restrict access to debug and other processor registers in the hardware, allowing a crash of the host or guest OS |
| CVE-2021-3011 | virtual interrupt controller in a virtualization product allows crash of host by writing a certain invalid value to a register, which triggers a fatal error instead of returning an error code |
| CVE-2020-12446 | Driver exposes access to Model Specific Register (MSR) registers, allowing admin privileges. |
| CVE-2015-2150 | Virtualization product does not restrict access to PCI command registers, allowing host crash from the guest. |

## Real CVEs with this weakness

| CVE | Title | Severity | CVSS | EPSS | CISA KEV | Published |
| --- | --- | --- | --- | --- | --- | --- |
| CVE-2023-20599 | - | high | 7.9 | - | No | 2025-06-10 |
| CVE-2025-47385 | Improper Access Control for Register Interface in SCE-Mink | high | 7.8 | - | No | 2026-03-02 |
| CVE-2015-8325 | The do\_setup\_env function in session.c in sshd in OpenSSH through 7.2p2, when the UseLogin feature is enabled and PAM is configured to read .pam\_environment files in user home directories, allows local users to gain privileges by triggering a crafted environment for the /bin/login program, as demonstrated by an LD\_PRELOAD environment variable. | high | 7.8 | - | No | 2016-05-01 |
| CVE-2024-6354 | - | high | 7.2 | - | No | 2024-06-26 |
| CVE-2025-33207 | - | medium | 6.8 | - | No | 2026-09-29 |
| CVE-2024-45556 | Improper Access Control for Register Interface in TZ Firmware | medium | 6.5 | - | No | 2025-04-07 |
| CVE-2024-57492 | - | medium | 6.0 | - | No | 2025-03-10 |
| CVE-2025-20788 | - | medium | 4.4 | - | No | 2025-12-02 |
| CVE-2025-54509 | - | medium | 4.0 | - | No | 2026-06-09 |
| CVE-2025-36194 | This Power System update is being released to address | low | 3.3 | - | No | 2026-02-02 |
| CVE-2025-1882 | i-Drive i11/i12 Device Setting improper access control for register interface | low | 2.3 | - | No | 2025-03-03 |

## Related attack patterns (CAPEC)

- [CAPEC-680](https://radicalnotion.ai/capec/capec-680): Exploitation of Improperly Controlled Registers

## Related weaknesses

| Relationship | CWE | Name |
| --- | --- | --- |
| Parent | [CWE-284](https://radicalnotion.ai/cwe/cwe-284) | Improper Access Control |
| Parent | [CWE-1220](https://radicalnotion.ai/cwe/cwe-1220) | Insufficient Granularity of Access Control |
| Peer | [CWE-1299](https://radicalnotion.ai/cwe/cwe-1299) | Missing Protection Mechanism for Alternate Hardware Interface |

## Frequently asked questions

### What is CWE-1262?

The product uses memory-mapped I/O registers that act as an interface to hardware functionality from software, but there is improper access control to those registers.

### What CVEs are caused by CWE-1262?

11 recorded CVEs are attributed to CWE-1262, including CVE-2023-20599, CVE-2025-47385 and CVE-2015-8325.

### How do you prevent CWE-1262?

Design proper policies for hardware register access from software.

### How is CWE-1262 detected?

Manual Analysis: This is applicable in the Architecture phase before implementation started. Make sure access policy is specified for the entire memory map. Manual analysis may not ensure the implementation is correct.

### What are the consequences of CWE-1262?

Exploiting CWE-1262 can lead to: Read Memory, Read Application Data, Modify Memory, Modify Application Data, Gain Privileges or Assume Identity, Bypass Protection Mechanism.

### Is CWE-1262 actively exploited?

11 recorded CVEs are caused by CWE-1262; none are currently in CISA's KEV catalog of actively exploited flaws.

Primary source: [MITRE CWE](https://cwe.mitre.org/data/definitions/1262.html)

---

Source: [RadicalNotion.AI](https://radicalnotion.ai/cwe/cwe-1262). Licensed CC BY-NC 4.0; attribute RadicalNotion.AI and link the source page when you reuse this data.
