背景詳情
引入方式
Array : Applications may use caches to improve efficiency
when communicating with remote entities or performing
intensive calculations.
適用平台
程式語言
類別: Not Language-Specific (Undetermined)
常見後果
| 範圍 |
影響 |
可能性 |
| Confidentiality | Read Application Data
注意:If the cache is accessible to unauthorized actors, attackers can read the cache and obtain this sensitive information. | |
觀察到的案例
| 參考資料 |
描述 |
| Product does not set the "no-cache" option in the HTTP Cache-Control header, allowing sensitive information to be cached |
潛在緩解措施
Phases : Architecture and Design
Protect information stored in cache.
Phases : Architecture and Design
Do not store unnecessarily sensitive information in the cache.
Phases : Architecture and Design
Consider using encryption in the cache.
偵測方法
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
有效性 : High
漏洞對應備注
理由說明 : 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-204 |
Lifting Sensitive Data Embedded in Cache
An adversary examines a target application's cache, or a browser cache, for sensitive information. Many applications that communicate with remote entities or which perform intensive calculations utilize caches to improve efficiency. However, if the application computes or receives sensitive information and the cache is not appropriately protected, an attacker can browse the cache and retrieve this information. This can result in the disclosure of sensitive information. |
提交
| 名稱 |
機構 |
日期 |
發布日期 |
Version |
| Anonymous Tool Vendor (under NDA) |
|
2006-07-19 +00:00 |
2006-07-19 +00:00 |
Draft 3 |
修改記錄
| 名稱 |
機構 |
日期 |
備註 |
| Eric Dalci |
Cigital |
2008-07-01 +00:00 |
updated Potential_Mitigations, Time_of_Introduction |
| CWE Content Team |
MITRE |
2008-09-08 +00:00 |
updated Relationships, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2011-03-29 +00:00 |
updated Name |
| CWE Content Team |
MITRE |
2011-06-01 +00:00 |
updated Common_Consequences, Relationships, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2012-05-11 +00:00 |
updated Relationships, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2012-10-30 +00:00 |
updated Potential_Mitigations |
| CWE Content Team |
MITRE |
2014-07-30 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2017-01-19 +00:00 |
updated Related_Attack_Patterns |
| CWE Content Team |
MITRE |
2017-11-08 +00:00 |
updated Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated Description, Name, Relationships, Type |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Detection_Factors, Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Applicable_Platforms, Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-04-30 +00:00 |
updated Observed_Examples |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Background_Details, Common_Consequences, Description, Modes_of_Introduction, Time_of_Introduction |