Dynamic tests should be performed to stress-test temperature controls.
CWE-1338 Base Rascunho
Improper Protections Against Hardware Overheating
This vulnerability occurs when a hardware device lacks sufficient safeguards to prevent dangerous temperature increases during operation.
Definição
What is CWE-1338?
This vulnerability occurs when a hardware device lacks sufficient safeguards to prevent dangerous temperature increases during operation.
All electronic devices generate heat as a byproduct of their operation. Faster processors and higher power draw create more thermal energy. Without built-in protections like temperature sensors, adequate cooling, or power throttling, this heat can build up uncontrollably. Malicious software can exploit this by forcing the hardware into high-performance states, deliberately triggering overheating to cause a temporary malfunction or permanent physical damage—a technique known as a thermal denial-of-service attack.
The consequences extend beyond security, impacting device safety and long-term reliability. While similar issues exist for overvoltage or overcurrent conditions, overheating is uniquely tied to normal hardware activity. It's important to note that while these protections guard against operational heat, they do not address separate failure modes like battery malfunctions, which require their own mitigation strategies.
Impacto no mundo real
Real-world CVEs caused by CWE-1338
Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Malicious software running on a core can execute instructions that consume maximum power or increase core frequency. Such a power-virus program could execute on the platform for an extended time to overheat the device, resulting in permanent damage.
- 2
Execution core and platform do not support thermal sensors, performance throttling, or platform-cooling countermeasures to ensure that any software executing on the system cannot cause overheating past the maximum allowable temperature.
- 3
The platform and SoC should have failsafe thermal limits that are enforced by thermal sensors that trigger critical temperature alerts when high temperature is detected. Upon detection of high temperatures, the platform should trigger cooling or shutdown automatically.
Exemplo de código vulnerável
Vulnerable pseudo
A MITRE não publicou um exemplo de código para este CWE. O padrão abaixo é ilustrativo — consulte os Recursos para referências canónicas.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} Exemplo de código seguro
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de verificação de prevenção
How to prevent CWE-1338
- Architecture and Design Temperature maximum and minimum limits should be enforced using thermal sensors both in silicon and at the platform level.
- Implementation The platform should support cooling solutions such as fans that can be modulated based on device-operation needs to maintain a stable temperature.
Sinais de deteção
How to detect CWE-1338
Power management controls should be part of Architecture and Design reviews.
CWE-1338
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.
Perguntas frequentes O que é o CWE-1338?
Qual a gravidade do CWE-1338?
Que linguagens ou plataformas são afetadas pelo CWE-1338?
Como posso prevenir o CWE-1338?
Como é que o Plexicus deteta e corrige o CWE-1338?
Onde posso saber mais sobre o CWE-1338?
Frequently asked questions
O que é o CWE-1338?
This vulnerability occurs when a hardware device lacks sufficient safeguards to prevent dangerous temperature increases during operation.
Qual a gravidade do CWE-1338?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-1338?
MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, Not Technology-Specific, ICS/OT, Power Management Hardware, Processor Hardware.
Como posso prevenir o CWE-1338?
Temperature maximum and minimum limits should be enforced using thermal sensors both in silicon and at the platform level. The platform should support cooling solutions such as fans that can be modulated based on device-operation needs to maintain a stable temperature.
Como é que o Plexicus deteta e corrige o CWE-1338?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-1338 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-1338?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/1338.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-1338
CWE-693 Pai
Protection Mechanism Failure
This weakness occurs when software either lacks a necessary security control, implements one that is too weak, or fails to activate an…
CWE-1039 Irmão
Inadequate Detection or Handling of Adversarial Input Perturbations in Automated Recognition Mechanism
This vulnerability occurs when a system uses automated AI or machine learning to classify complex inputs like images, audio, or text, but…
CWE-1248 Irmão
Semiconductor Defects in Hardware Logic with Security-Sensitive Implications
A security-critical hardware component contains physical flaws in its semiconductor material, which can cause it to malfunction and…
CWE-1253 Irmão
Incorrect Selection of Fuse Values
This vulnerability occurs when a hardware security fuse is incorrectly programmed to represent a 'secure' state as logic 0 (unblown). An…
CWE-1269 Irmão
Product Released in Non-Release Configuration
This vulnerability occurs when a product ships to customers while still configured with its pre-production or manufacturing settings,…
CWE-1278 Irmão
Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques
This vulnerability occurs when hardware lacks safeguards against physical inspection, allowing attackers to extract sensitive data by…
CWE-1291 Irmão
Public Key Re-Use for Signing both Debug and Production Code
This vulnerability occurs when the same cryptographic key is used to sign both development/debug software builds and final production…
CWE-1318 Irmão
Missing Support for Security Features in On-chip Fabrics or Buses
This vulnerability occurs when the communication channels (fabrics or buses) within a chip lack built-in or enabled security features,…
CWE-1319 Irmão
Improper Protection against Electromagnetic Fault Injection (EM-FI)
This vulnerability occurs when a hardware device lacks sufficient shielding against electromagnetic interference, allowing attackers to…
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.