← Back to Baseline

MB-0791

Automated Custom source avoids eval and create_function constructs

MB-C03 Secure Coding Practices Medium

Collected custom PHP/PHTML contains no eval construct or direct global create_function call. Dynamic include targets, indirect calls, function aliases and unresolved assertion semantics yield UNKNOWN. This is a construct policy, not general runtime execution assurance. Scope is completely collected app/code PHP/PHTML; missing, unreadable, oversized, linked, malformed or truncated eligible input prevents a clean PASS.

Overview

Collected custom PHP/PHTML contains no eval construct or direct global create_function call. Dynamic include targets, indirect calls, function aliases and unresolved assertion semantics yield UNKNOWN. This is a construct policy, not general runtime execution assurance. Scope is completely collected app/code PHP/PHTML; missing, unreadable, oversized, linked, malformed or truncated eligible input prevents a clean PASS.

Why it Matters

Runtime-created code obscures the set of operations a reviewer can inspect in advance. An exact eval/create_function ban makes one high-impact construct choice explicit.

It does not cover every dynamic include or language-version-dependent execution mechanism.

Verification Steps

Manual Verification

  1. Review actual eval constructs and global create_function calls, excluding comments/literal text.
  2. Trace dynamic include and assertion cases separately and retain unresolved ambiguity.
  3. Confirm complete PHP/PHTML collection.

Command / Review Sample

// Explicit dispatch illustration:
switch ($operation) { case 'refresh': $service->refresh(); break; default: throw new InvalidArgumentException(); }

Use the assessed Magento project and the appropriate application or read-only review account. Replace example hosts, paths and identifiers with the assessment scope; configuration and source fragments are illustrative.

Remediation / Fix Guidance

  1. Inspect each named call and argument at the reported file/line. Trace input origin, receiver identity, authorization and output use before deciding whether to replace the API or document an approved exception to this explicit coding policy.
  2. Test the affected behavior and its real trust boundary. Replacing an API or wrapping a call does not by itself validate input or remove an exploit path.
  3. Rerun MB-0791 against the same release, profile and relevant file/key/package scope; compare the new evidence and inspect any independent collection gaps.

Examples

Illustrative examples only. Interpret them within the current revision criterion above; missing collection evidence is unresolved, never PASS.

Fail Example

eval($expression);

Pass Example

switch ($operation) {
    case 'refresh': $service->refresh(); break;
    default: throw new InvalidArgumentException();
}
// Explicit dispatch; review operation authorization separately.

Scope and Evidence Limits

Rule revision: 1. Target modes: LOCAL.

Collected custom PHP/PHTML contains no eval construct or direct global create_function call. Dynamic include targets, indirect calls, function aliases and unresolved assertion semantics yield UNKNOWN. This is a construct policy, not general runtime execution assurance. Scope is completely collected app/code PHP/PHTML; missing, unreadable, oversized, linked, malformed or truncated eligible input prevents a clean PASS.

Exact opt-in coding policy, not a finding of confirmed exploitability or proof of the broader historical requirement. Runtime adapters, dependencies, generated code and files outside app/code remain outside this predicate.

Catalog coverage describes implementation capability, not a scan outcome. An incomplete manual review cannot establish that the criterion is satisfied.

References