Repository navigation
research: trace and probe Base64 fallible-allocation boundary - #4
Conversation
Verified Base64 OOM allocation evidenceSource: GitHub Actions run #39993301060, downloaded
Exact hard-limit allocation request: 18,178,048 bytes (both versions). Hard limit: 33,554,432 bytes. Comparison job passed and reported Static inspection of pinned PHP 8.5.12 demonstrates Base64 C callers in The permanent report and compact evidence are now committed to Status: reproduced public GH-24492 behavior, not a new vulnerability; not yet a core bug fix. Do not submit duplicate upstream patch while #24548 and related work remain open. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Context
Follow-up to #2 and upstream php/php-src#24492.
This adds a bounded observation of
base64_encode()memory-exhaustion behavior, which upstream PR #24548 explicitly leaves out of scope due to its exported C helper's caller contracts.What changed
base64_encode_growthtest in a disposable CI process.php/php-src, no unpatched historical releases, no zero-day or exploit PoC.Verification gates
We must not turn the exported C helper nullable without auditing every caller.