Summary
Phison PS3111-S11 controller firmware versions through SBFQT1.3 expose privileged vendor unique commands over the ATA interface without reliable authentication.
An attacker with suitable ATA access may bypass the unlock mechanism or use an unlocked build to read and modify controller memory and raw flash, potentially enabling persistent firmware-level implants.
Affected context
The vulnerability affects systems using Phison PS3111-S11 controller firmware through SBFQT1.3 where vendor unique commands are reachable through the ATA interface. Risk is higher when an attacker can obtain direct or indirect storage-device access and the firmware either lacks a VUC lock or relies on the weak CRC-16-based unlock handshake.
Exploit preconditions
- Attack surface: ATA interface and exposed vendor unique controller commands
- Required access: Ability to communicate with the affected storage device at the ATA command level
- Trigger point: Authentication or unlock processing for privileged vendor commands
- Why exploitation is possible: Authentication may be absent or bypassable, allowing privileged operations against controller memory and raw flash
Why this happens
The underlying issue is missing or ineffective authentication for privileged vendor-specific commands. Firmware configurations that expose these operations without a mandatory access-control check, or that rely on a weak and defeatable unlock handshake, allow an untrusted command issuer to reach sensitive controller functionality. This maps to CWE-306: Missing Authentication for Critical Function.
Potential impact
- An attacker may read sensitive data from controller memory or raw flash
- An attacker could modify firmware-relevant memory or storage contents
- Malicious changes may persist across power cycles
- A threat actor could implant unauthorized controller-level behavior
- Storage integrity, availability, or confidentiality may be compromised
General mitigation guidance
Mitigation generally focuses on enforcing authentication and authorization for every privileged vendor command.
Common defensive patterns include:
- Require strong, cryptographically sound authentication before enabling vendor unique commands
- Disable or remove diagnostic and manufacturing command paths in production firmware
- Reject privileged operations by default when authentication state is absent or invalid
- Separate service, manufacturing, and end-user command privileges
- Protect signing keys and use authenticated firmware and controller updates
- Limit physical and logical access to ATA interfaces through platform and device policy
- Apply least-privilege controls to systems that can issue low-level storage commands
How teams detect issues like this
Organizations can assess this class of issue through:
- Firmware review for vendor command handlers that lack mandatory authentication gates
- Static analysis of unlock routines, CRC-based authorization logic, and command dispatch paths
- Dynamic testing that verifies privileged commands remain inaccessible before authentication
- Code review checks for production builds that retain manufacturing or debug interfaces
- Device policy enforcement and telemetry for unusual low-level ATA command activity
- Automated firmware analysis and security review tools that flag missing authorization checks

