← Back to Baseline

MB-0790

Automated Custom source avoids enumerated shell/process primitives

MB-C03 Secure Coding Practices Medium

Collected custom PHP/PHTML contains no direct global exec/system/passthru/shell_exec/popen/proc_open/pcntl_exec invocation or shell backtick expression. Indirect calls and function aliases yield UNKNOWN; framework process adapters are outside this API ban. 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 direct global exec/system/passthru/shell_exec/popen/proc_open/pcntl_exec invocation or shell backtick expression. Indirect calls and function aliases yield UNKNOWN; framework process adapters are outside this API ban. Scope is completely collected app/code PHP/PHTML; missing, unreadable, oversized, linked, malformed or truncated eligible input prevents a clean PASS.

Why it Matters

Direct process primitives and shell expressions create extra execution paths inside application code. Restricting those paths reduces the number of places needing command-boundary review.

Approved adapters and indirect execution remain outside the direct-call predicate and need their own assessment.

Verification Steps

Manual Verification

  1. Inspect direct exec/system/passthru/shell_exec/popen/proc_open/pcntl_exec calls and shell backtick expressions.
  2. Resolve namespace/alias ambiguity and verify complete collection.
  3. Review alternative process services under their own validation policy.

Command / Review Sample

// Prohibited source illustration:
$output = shell_exec($command);
// Prefer an approved operation-specific service after separate review.

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-0790 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

$output = shell_exec($command);

Pass Example

$result = $reportService->build($validatedRequest);
// Illustrative operation-specific service, not a shell expression.
// Review any internal process adapter independently.

Scope and Evidence Limits

Rule revision: 1. Target modes: LOCAL.

Collected custom PHP/PHTML contains no direct global exec/system/passthru/shell_exec/popen/proc_open/pcntl_exec invocation or shell backtick expression. Indirect calls and function aliases yield UNKNOWN; framework process adapters are outside this API ban. 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