Create a new installable boot image of the current build with a minor version number change. Use the standard installation method to update the boot image. Verify that the minor version number has changed. Create a fake image. Verify that the boot updater will not install the fake image and generates an "invalid image" error message or equivalent.
CWE-1277 Base Borrador
Firmware Not Updateable
This vulnerability occurs when a hardware product lacks a mechanism for users to install firmware updates, leaving known security flaws permanently unpatched.
Definición
What is CWE-1277?
This vulnerability occurs when a hardware product lacks a mechanism for users to install firmware updates, leaving known security flaws permanently unpatched.
When firmware cannot be updated, every security vulnerability discovered after manufacture becomes a permanent, unfixable flaw in the device. This exposes users to potential exploitation for the entire lifespan of the product—which could span decades—effectively locking in security risks.
While network-level protections or monitoring can offer some external mitigation, they cannot address the core vulnerability within the device itself. This limitation places the long-term security burden entirely on the user and highlights a critical design failure in the product's lifecycle management.
Impacto en el mundo real
Real-world CVEs caused by CWE-1277
-
Chain: network-attached storage (NAS) device has a critical OS command injection (CWE-78) vulnerability that is actively exploited to place IoT devices into a botnet, but some products are "end-of-support" and cannot be patched (CWE-1277). [REF-1097]
-
A hardware "smart lock" has weak key generation that allows attackers to steal the key by BLE sniffing, but the device's firmware cannot be upgraded and hence remains vulnerable [REF-1095].
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
Identifica una ruta de código que maneje entrada no confiable sin validación.
- 2
Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.
- 3
Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.
- 4
Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.
Ejemplo de código vulnerable
Vulnerable Other
A refrigerator has an Internet interface for the official purpose of alerting the manufacturer when that refrigerator detects a fault. Because the device is attached to the Internet, the refrigerator is a target for hackers who may wish to use the device other potentially more nefarious purposes.
The refrigerator has no means of patching and is hacked becoming a spewer of email spam. Ejemplo de código seguro
Secure Other
The device automatically patches itself and provides considerable more protection against being hacked. What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de prevención
How to prevent CWE-1277
- Requirements Specify requirements to include the ability to update the firmware. Include integrity checks and authentication to ensure that untrusted firmware cannot be installed.
- Architecture and Design Design the device to allow for updating the firmware. Ensure that the design specifies how to distribute the updates and ensure their integrity and authentication.
- Implementation Implement the necessary functionality to allow the firmware to be updated.
Señales de detección
How to detect CWE-1277
Check the consumer or maintainer documentation, the architecture/design documentation, or the original requirements to ensure that the documentation includes details for how to update the firmware.
Determine if there is a lack of a capability to update read-only memory (ROM) structure. This could manifest as a difference between the latest firmware version and the current version within the device.
CWE-1277
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Preguntas frecuentes ¿Qué es CWE-1277?
¿Qué gravedad tiene CWE-1277?
¿Qué lenguajes o plataformas se ven afectados por CWE-1277?
¿Cómo puedo prevenir CWE-1277?
¿Cómo detecta y corrige Plexicus CWE-1277?
¿Dónde puedo aprender más sobre CWE-1277?
Frequently asked questions
¿Qué es CWE-1277?
This vulnerability occurs when a hardware product lacks a mechanism for users to install firmware updates, leaving known security flaws permanently unpatched.
¿Qué gravedad tiene CWE-1277?
MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.
¿Qué lenguajes o plataformas se ven afectados por CWE-1277?
MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, Not Technology-Specific.
¿Cómo puedo prevenir CWE-1277?
Specify requirements to include the ability to update the firmware. Include integrity checks and authentication to ensure that untrusted firmware cannot be installed. Design the device to allow for updating the firmware. Ensure that the design specifies how to distribute the updates and ensure their integrity and authentication.
¿Cómo detecta y corrige Plexicus CWE-1277?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-1277 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.
¿Dónde puedo aprender más sobre CWE-1277?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/1277.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-1277
CWE-1329 Padre
Reliance on Component That is Not Updateable
This vulnerability occurs when a product depends on a component that cannot be updated or patched to fix security flaws or critical bugs.
CWE-1310 Hermano
Missing Ability to Patch ROM Code
A system or System-on-Chip (SoC) lacks a mechanism to update its initial boot code stored in Read-Only Memory (ROM), permanently exposing…
Recursos
Further reading
- MITRE — CWE-1277 oficial https://cwe.mitre.org/data/definitions/1277.html
- Bad news: KeyWe Smart Lock is easily bypassed and can't be fixed https://www.theregister.com/2019/12/11/f_secure_keywe/
- Alarm bells ring, the IoT is listening https://www.computerweekly.com/news/252475324/Alarm-bells-ring-the-IoT-is-listening
- Zyxel Flaw Powers New Mirai IoT Botnet Strain https://krebsonsecurity.com/2020/03/zxyel-flaw-powers-new-mirai-iot-botnet-strain/
¿Listo para validar lo que importa?
Listo para validar lo que importa.
Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.