CWE-913 상세 정보

CWE-913

Improper Control of Dynamically-Managed Code Resources
2013-02-21
00h00 +00:00
Incomplete
2026-10-28
00h00 +00:00
특정 CWE 알림
특정 CWE의 변경 사항에 대한 정보를 받아보세요.
알림 관리

이름: Improper Control of Dynamically-Managed Code Resources

The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.

일반 정보

배경 세부 정보

취약점 도입 방식

Architecture and Design
Implementation

적용 가능한 플랫폼

언어

클래스: Not Language-Specific (Undetermined)
클래스: Interpreted (Undetermined)

일반적인 결과

범위 영향 가능성
IntegrityExecute Unauthorized Code or Commands
Other
Integrity
Varies by Context, Alter Execution Logic

관찰된 예시

참고 자료 설명

CVE-2022-2054

Python compiler uses eval() to execute malicious strings as Python code.

CVE-2018-1000613

Cryptography API uses unsafe reflection when deserializing a private key

CVE-2015-8103

Deserialization issue in commonly-used Java library allows remote execution.

CVE-2006-7079

Chain: extract used for register_globals compatibility layer, enables path traversal (CWE-22)

CVE-2012-2055

Source version control product allows modification of trusted key using mass assignment.

잠재적 완화 방법

Phases : Implementation
For any externally-influenced input, check the input against an allowlist of acceptable values.
Phases : Implementation // Architecture and Design
Refactor the code so that it does not need to be dynamically managed.

탐지 방법

Fuzzing

Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.
효과성 : High

취약점 매핑 메모

근거 : This CWE entry is a Class and might have Base-level children that would be more appropriate
댓글 : Examine children of this entry to see if there is a better fit

제출

이름 조직 날짜 출시일 Version
CWE Content Team MITRE 2013-01-26 +00:00 2013-02-21 +00:00 2.4

수정 사항

이름 조직 날짜 댓글
CWE Content Team MITRE 2015-12-07 +00:00 updated Relationships
CWE Content Team MITRE 2017-01-19 +00:00 updated Relationships
CWE Content Team MITRE 2017-11-08 +00:00 updated Relationships
CWE Content Team MITRE 2019-06-20 +00:00 updated Relationships
CWE Content Team MITRE 2020-02-24 +00:00 updated Relationships
CWE Content Team MITRE 2020-06-25 +00:00 updated Potential_Mitigations
CWE Content Team MITRE 2021-10-28 +00:00 updated Relationships
CWE Content Team MITRE 2023-01-31 +00:00 updated Description
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 2023-10-26 +00:00 updated Observed_Examples
CWE Content Team MITRE 2025-12-11 +00:00 updated Applicable_Platforms, Demonstrative_Examples, Weakness_Ordinalities
CWE Content Team MITRE 2026-10-28 +00:00 updated Background_Details, Description