CWE-540 상세 정보

CWE-540

Inclusion of Sensitive Information in Source Code
2006-07-19
00h00 +00:00
Incomplete
2026-10-28
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)

일반적인 결과

범위 영향 가능성
ConfidentialityRead 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 Configuration
Recommendations 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) 2006-07-19 +00:00 2006-07-19 +00:00 Draft 3

수정 사항

이름 조직 날짜 댓글
Eric Dalci Cigital 2008-07-01 +00:00 updated Time_of_Introduction
CWE Content Team MITRE 2008-09-08 +00:00 updated Relationships, Taxonomy_Mappings
CWE Content Team MITRE 2008-10-14 +00:00 updated Description
CWE Content Team MITRE 2009-03-10 +00:00 updated Relationships
CWE Content Team MITRE 2011-03-29 +00:00 updated Description, Name
CWE Content Team MITRE 2011-06-01 +00:00 updated Common_Consequences
CWE Content Team MITRE 2012-05-11 +00:00 updated Relationships
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-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 2021-10-28 +00:00 updated Relationships
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 2023-10-26 +00:00 updated Demonstrative_Examples, Observed_Examples
CWE Content Team MITRE 2025-12-11 +00:00 updated Applicable_Platforms, Detection_Factors, Relationships, Weakness_Ordinalities
CWE Content Team MITRE 2026-10-28 +00:00 updated Common_Consequences, Description, Potential_Mitigations