This vulnerability occurs when a product ships to customers while still configured with its pre-production or manufacturing settings, which typically include powerful debugging and testing features not intended for real-world use.
Products under development or in manufacturing are configured with extensive debug capabilities to aid engineers. These often include backdoors to bypass security checks (like authentication or encryption), commands to read or modify internal memory and registers, hidden administrative functions, and the ability to alter critical system configurations. These features, while necessary for testing, create severe security gaps if they remain accessible after the product ships. The risk is especially high in complex supply chains involving multiple vendors. For example, a chip manufacturer might test a component and then send it to an OEM for further testing before final production. The product is only considered secure for release after all testing is complete and a final lock-down step (like blowing a 'Manufacturing Complete' fuse) is performed. If this final step is missed, the product remains in its vulnerable, high-access manufacturing state, exposing end-users to potential attacks.
Impact: Other
Suppose the chipmaker has a way of scanning all the internal memory (containing chipmaker-level secrets) during the manufacturing phase, and the way the chipmaker or the Original Equipment Manufacturer (OEM) marks the end of the manufacturing phase is by blowing a Manufacturing Complete fuse. Now, suppose that whoever blows the Manufacturing Complete fuse inadvertently forgets to execute the step to blow the fuse.
Blow the Manufacturing Complete fuse.