CWE-1314 詳細

CWE-1314

Missing Write Protection for Parametric Data Values
2020-12-10
00h00 +00:00
Draft
2026-10-28
00h00 +00:00
特定のCWEの通知
特定のCWEの変更情報をいち早くお届けします。
通知を管理する

名前: Missing Write Protection for Parametric Data Values

The device does not write-protect the parametric data values for sensors that scale the sensor value, allowing untrusted software to manipulate the apparent result and potentially damage hardware or cause operational failure.

一般情報

背景の詳細

導入モード

Architecture and Design : The lack of a requirement to protect parametric values may contribute to this weakness.
Implementation : The lack of parametric value protection may be a cause of this weakness.

適用可能なプラットフォーム

言語

クラス: Not Language-Specific (Undetermined)

オペレーティングシステム

クラス: Not OS-Specific (Undetermined)

アーキテクチャ

クラス: Not Architecture-Specific (Undetermined)

テクノロジー

名前: Sensor Hardware (Undetermined)

一般的な結果

スコープ 影響 可能性
AvailabilityQuality Degradation, DoS: Resource Consumption (Other), DoS: Crash, Exit, or Restart

注記:Sensor value manipulation, particularly thermal or power, may allow physical damage to occur or disabling of the device by a false fault shutdown causing a Denial-Of-Service.
High

観察された例

参考文献 説明

CVE-2017-8252

Kernel can inject faults in computations during the execution of TrustZone leading to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice and Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking.

潜在的な緩和策

Phases : Architecture and Design
Access controls for sensor blocks should ensure that only trusted software is allowed to change threshold limits and sensor parametric data.

脆弱性マッピングノート

理由 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
コメント : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

関連する攻撃パターン

CAPEC ID 攻撃パターン名
CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs
In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.

参考文献

REF-1082

CLKSCREW: Exposing the Perils of Security-Oblivious Energy Management
Adrian Tang, Simha Sethumadhavan, Salvatore Stolfo.
https://www.usenix.org/system/files/conference/usenixsecurity17/sec17-tang.pdf

登録情報

名前 組織 日付 リリース日 Version
Hareesh Khattri, Parbati K. Manna, and Arun Kanuparthi Intel Corporation 2020-07-14 +00:00 2020-12-10 +00:00 4.3

変更履歴

名前 組織 日付 コメント
CWE Content Team MITRE 2022-04-28 +00:00 updated Applicable_Platforms
CWE Content Team MITRE 2022-06-28 +00:00 updated Applicable_Platforms
CWE Content Team MITRE 2023-04-27 +00:00 updated Relationships
CWE Content Team MITRE 2023-06-29 +00:00 updated Mapping_Notes
CWE Content Team MITRE 2025-12-11 +00:00 updated Weakness_Ordinalities
CWE Content Team MITRE 2026-10-28 +00:00 updated Background_Details, Common_Consequences, Description