PUK

PIN Unblocking Key

Security
Introduced in Rel-6
A secret code used to unblock a SIM/USIM card when the Personal Identification Number (PIN) has been entered incorrectly too many times, locking the card. It restores access to the card's services without erasing stored data.

Description

The PIN Unblocking Key (PUK) is a security feature integral to the UICC (Universal Integrated Circuit Card), which houses the SIM (Subscriber Identity Module) or USIM (Universal Subscriber Identity Module) application. Its primary function is to recover access to the UICC after the user has been locked out due to consecutive incorrect entries of the Personal Identification Number (PIN). The PIN itself protects access to the UICC's functionalities, such as making network attachments or accessing stored contacts. After a configurable number of failed PIN attempts (typically 3), the UICC becomes 'PIN-blocked,' disabling its normal operations.

Architecturally, the PUK is an 8-digit code that is distinct from the PIN and is pre-programmed into the UICC by the operator during personalization. It is stored securely within the card's file system, often in the EF_AD (Administrative Data) file. The PUK is not meant for daily use and is typically provided to the subscriber separately from the PIN, often printed on the card holder or communicated via a secure channel. The process involves the user entering the PUK via the device's interface, followed by a new PIN and its verification. If entered correctly, the PUK resets the PIN attempt counter and allows the new PIN to be set, unblocking the card.

If the PUK itself is entered incorrectly a certain number of times (usually 10), the UICC becomes permanently 'PUK-blocked.' In this state, the card is rendered unusable for network access as it irreversibly locks the security functions. The only recourse is to obtain a new UICC from the mobile operator, as the old one cannot be recovered. This two-tier security mechanism (PIN and PUK) balances user convenience with protection against brute-force attacks. The PUK procedure is standardized in 3GPP TS 31.101 (UICC-terminal interface) and related specifications, ensuring interoperability across devices and networks.

Purpose & Motivation

The PUK was created to address a critical usability problem inherent in PIN-based security: the inevitability of user error. Without a recovery mechanism, forgetting a PIN or making repeated input mistakes (e.g., by a child) would permanently lock a valuable hardware token (the SIM card), forcing a physical replacement and causing service disruption. The PUK provides a secure 'safety net' that allows legitimate users to regain control of their subscription and device.

Historically, as mobile devices became personal repositories of data and identity, the security of the SIM card became paramount. The PIN was introduced to prevent unauthorized use if the device was lost or stolen. However, a purely punitive lockout mechanism was commercially and practically unacceptable. The PUK solves this by offering a one-time recovery path that maintains security. It is a compromise that thwarts casual guessing (due to the separate, longer PUK code and its own attempt limit) while providing a manageable customer service process for operators. Its creation was motivated by the need to make strong device and network access security (via the PIN) palatable and practical for millions of everyday users, thereby enabling the widespread adoption of SIM-locking features.

Key Features

  • 8-digit secret code used to unblock a PIN-locked UICC (SIM/USIM)
  • Pre-programmed by the mobile operator during card personalization
  • Resets the PIN attempt counter and allows a new PIN to be set
  • Has its own attempt counter (typically 10); exceeding it permanently blocks the card
  • Stored securely in the UICC's file system (e.g., EF_AD)
  • Standardized procedure defined in 3GPP TS 31.101 and related specs

Evolution Across Releases

Rel-6 Initial

Introduced the standardized PIN Unblocking Key (PUK) procedures for USIM applications in the context of 3G/WCDMA. Defined the fundamental architecture where the PUK is stored on the UICC, the unblocking process via the terminal, and the consequences of PUK failure, establishing the core security and recovery mechanism.

Minor refinements and maintenance of UICC security specifications. Ensured backward compatibility and clarity in PUK-related procedures as part of broader USIM and card application toolkit enhancements.

Maintained PUK functionality for the new EPS/LTE ecosystem. The USIM for LTE continued to use the same PUK mechanisms, ensuring security continuity for subscribers migrating to 4G services.

Continued support within evolving UICC standards. No major changes to the core PUK concept, as it remained a stable and essential subscriber security feature.

Ongoing inclusion in UICC and security specifications. The PUK mechanism was considered mature and continued to be mandated for USIM applications.

Maintenance of the feature as part of the broader 3GPP security framework. Ensured interoperability for new device form factors and embedded SIM (eSIM) considerations began to emerge.

Support for PUK in the context of Machine-Type Communication (MTC) where remote SIM provisioning might be used, though the fundamental local unblocking procedure remained unchanged.

Continued specification maintenance. The PUK remained a baseline security requirement for traditional UICCs.

Enhanced support for remote management and provisioning with the formal introduction of the eSIM (embedded UICC) architecture in 3GPP. While the PUK concept persisted, new remote SIM provisioning protocols could offer alternative recovery methods.

Integration into the 5G security architecture for 5G SIM (5G USIM). The PUK remains a required feature for the UICC hosting the 5G USIM application, ensuring subscriber recovery for 5G devices.

Further evolution of eSIM and IoT security. PUK support is maintained for compliance and backward compatibility, even as some IoT devices might use alternative credential management systems.

Ongoing specification support within the 5G-Advanced timeline. The PUK is a legacy but vital feature supported in modern UICCs for consumer devices.

Maintenance and potential clarifications within the security specifications. The PUK mechanism is considered a stable, long-term part of the subscriber identity module security suite.

Continued inclusion in 3GPP specifications to ensure interoperability for all devices using UICC-based authentication, including those for 5G-Advanced and beyond.

Defining Specifications

SpecificationTitle
TS 21.905 3GPP TS 21.905
TS 31.113 3GPP TR 31.113