Chi tiết nền tảng
Các cách xuất hiện
Implementation : The dynamic identification of variables can be a
powerful, time-saving technique for developers. This
practice can reduce maintenance costs because new code
would not need to be written for each variable that is
managed.
Nền tảng áp dụng
Ngôn ngữ
Lớp: Not Language-Specific (Undetermined)
Lớp: Interpreted (Undetermined)
Hậu quả phổ biến
| Phạm vi |
Tác động |
Khả năng xảy ra |
| Integrity | Modify Application Data
Ghi chú: An attacker could modify sensitive data or critical program variables. | |
| Integrity | Execute Unauthorized Code or Commands | |
Other Integrity | Varies by Context, Alter Execution Logic | |
Ví dụ đã quan sát
| Tài liệu tham khảo |
Mô tả |
| extract issue enables file inclusion |
| Chain: extract used for register_globals compatibility layer, enables path traversal (CWE-22) |
| extract() buried in include files makes post-disclosure analysis confusing; original report had seemed incorrect. |
| extract() enables static code injection |
| import_request_variables() buried in include files makes post-disclosure analysis confusing |
| Chain: Dynamic variable evaluation allows resultant remote file inclusion and path traversal. |
| Chain: dynamic variable evaluation in PHP program used to modify critical, unexpected $_SERVER variable for resultant XSS. |
| Chain: dynamic variable evaluation in PHP program used to conduct remote file inclusion. |
| Dynamic variable evaluation in mail program allows reading and modifying attachments and preferences of other users. |
Các biện pháp giảm thiểu tiềm năng
Phases : Implementation
For any externally-influenced input, check the input against an allowlist of internal program variables that are allowed to be modified.
Phases : Implementation // Architecture and Design
Refactor the code so that internal program variables do not need to be dynamically identified.
Ghi chú ánh xạ lỗ hổng
Lý do : 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.
Bình luận : 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.
Gửi
| Tên |
Tổ chức |
Ngày |
Ngày phát hành |
Version |
| CWE Content Team |
MITRE |
2013-01-26 +00:00 |
2013-02-21 +00:00 |
2.4 |
Sửa đổi
| Tên |
Tổ chức |
Ngày |
Bình luận |
| CWE Content Team |
MITRE |
2017-01-19 +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 |
2023-01-31 +00:00 |
updated Description |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships, Time_of_Introduction |
| 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 |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Background_Details, Common_Consequences, Description, Modes_of_Introduction |