Description
The product uses external input to determine the names of variables into which information is extracted, without verifying that the names of the specified variables are valid. This could cause the program to overwrite unintended variables.
Modes of Introduction:
– Implementation
Related Weaknesses
Consequences
Integrity: Modify Application Data
An attacker could modify sensitive data or program variables.
Potential Mitigations
Phase: Implementation
Description:
Use allowlists of variable names that can be extracted.
Phase: Implementation
Description:
Consider refactoring your code to avoid extraction routines altogether.
Phase: Implementation
Description:
In PHP, call extract() with options such as EXTR_SKIP and EXTR_PREFIX_ALL; call import_request_variables() with a prefix argument. Note that these capabilities are not present in all PHP versions.
CVE References
- CVE-2006-7135
- extract issue enables file inclusion
- CVE-2006-7079
- extract used for register_globals compatibility layer, enables path traversal
- CVE-2007-0649
- extract() buried in include files makes post-disclosure analysis confusing; original report had seemed incorrect.
- CVE-2006-6661
- extract() enables static code injection
- CVE-2006-2828
- import_request_variables() buried in include files makes post-disclosure analysis confusing
More Stories
The Most Dangerous Vulnerabilities in Apache Tomcat and How to Protect Against Them
Apache Tomcat is an open-source web server and servlet container that is widely used in enterprise environments to run Java...
ZDI-CAN-18333: A Critical Zero-Day Vulnerability in Microsoft Windows
Zero-day vulnerabilities are a serious threat to cybersecurity, as they can be exploited by malicious actors to gain unauthorized access...
CWE-669 – Incorrect Resource Transfer Between Spheres
Description The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere,...
CWE-67 – Improper Handling of Windows Device Names
Description The software constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a...
CWE-670 – Always-Incorrect Control Flow Implementation
Description The code contains a control flow path that does not reflect the algorithm that the path is intended to...
CWE-671 – Lack of Administrator Control over Security
Description The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect...