이름: Exposure of Backup File to an Unauthorized Control Sphere

A backup file is stored in a directory or archive that is made accessible to unauthorized actors.

일반 정보

배경 세부 정보

취약점 도입 방식

Operation : OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.
Array : This renaming may have been performed automatically by the web server, or manually by the administrator.

적용 가능한 플랫폼

언어

클래스: Not Language-Specific (Undetermined)

기술

클래스: Not Technology-Specific (Undetermined)
이름: Web Server (Undetermined)

일반적인 결과

범위	영향	가능성
Confidentiality	Read Application Data 참고: At a minimum, an attacker who retrieves this file would have all the information contained in it, whether that be database calls, the format of parameters accepted by the application, or simply information regarding the architectural structure of your site. The source code for old files that were renamed in this manner and left in the webroot can often be retrieved.

관찰된 예시

참고 자료	설명
CVE-2024-7315	Chain: WordPress plugin does not use sufficient randomness when generating the filename for a backup (CWE-340), allowing attackers to obtain backup files (CWE-530)

잠재적 완화 방법

Phases : Policy
Recommendations include implementing a security policy within your organization that prohibits backing up web application source code in the webroot.

탐지 방법

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 Variant 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 Common_Consequences, Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2009-03-10 +00:00	updated Relationships
CWE Content Team	MITRE	2009-10-29 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2009-12-28 +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 Modes_of_Introduction, Relationships, Taxonomy_Mappings, Time_of_Introduction
CWE Content Team	MITRE	2020-02-24 +00:00	updated Description, Relationships
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

CWE-530 상세 정보

CWE-530