CWE-540
Inclusion of Sensitive Information in Source Code
2006-07-19
00h00 +00:00
00h00 +00:00
特定のCWEの通知
特定のCWEの変更情報をいち早くお届けします。
名前: Inclusion of Sensitive Information in Source Code
The product (such as a web server or repository) provides access to source code is not intended to be accessible to users but contains sensitive information.
一般情報
導入モード
Implementation適用可能なプラットフォーム
言語
クラス： Not Language-Specific (Undetermined)テクノロジー
クラス： Not Technology-Specific (Undetermined)クラス： Web Based (Undetermined)
一般的な結果
| スコープ | 影響 | 可能性 |
|---|---|---|
| Confidentiality | Read Application Data, Varies by Context 注記：Obtaining source code on a system allows an attacker to understand the logic of the script and extract extremely useful information such as code bugs or logins and passwords. |
観察された例
| 参考文献 | 説明 |
|---|---|
CVE-2022-25512 | Server for Team Awareness Kit (TAK) application includes sensitive tokens in the JavaScript source code. |
CVE-2022-24867 | The LDAP password might be visible in the html code of a rendered page in an IT Asset Management tool. |
CVE-2007-6197 | Version numbers and internal hostnames leaked in HTML comments. |
潜在的な緩和策
Phases : Architecture and Design // System ConfigurationRecommendations include removing the script from the web server and moving it to a location not accessible from the Internet.
検出方法
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.)脆弱性マッピングノート
理由 : 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.
登録情報
| 名前 | 組織 | 日付 | リリース日 | Version |
|---|---|---|---|---|
| Anonymous Tool Vendor (under NDA) | Draft 3 |
変更履歴
| 名前 | 組織 | 日付 | コメント |
|---|---|---|---|
| Eric Dalci | Cigital | updated Time_of_Introduction | |
| CWE Content Team | MITRE | updated Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Description, Name | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Potential_Mitigations | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Description, Name, Relationships, Type | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, Observed_Examples | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Detection_Factors, Relationships, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Common_Consequences, Description, Potential_Mitigations |
