CWE-621: Variable Extraction Error

Variant

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.

For example, in PHP, extraction can be used to provide functionality similar to register_globals, a dangerous functionality that is frequently disabled in production systems. Calling extract() or import_request_variables() without the proper arguments could allow arbitrary global variables to be overwritten, including superglobals. Similar functionality is possible in other interpreted languages, including custom languages.

Consequences

Integrity: Modify Application Data

How to prevent it

Implementation: Use allowlists of variable names that can be extracted.
Implementation: Consider refactoring your code to avoid extraction routines altogether.
Implementation: 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.

Recent advisories

GHSA-x962-w72p-mv7q — phpMyAdmin Global variables scope injection vulnerability

All advisories for CWE-621

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor