CurlHeadersIncludedInDecodedBody

warning native on by default

Group: Probable bugs

Including response headers in a cURL return value makes the combined data unsuitable for JSON decoding. Capture headers separately from the body.

Example

<?php
$h=curl_init();curl_setopt($h,CURLOPT_HEADER,true);curl_setopt($h,CURLOPT_RETURNTRANSFER,true);json_decode(curl_exec($h));

Reported:

• line 2: Keep HTTP headers separate from the decoded JSON body.

Detection

• Same resolved curl handle has definite CURLOPT_HEADER=true and CURLOPT_RETURNTRANSFER=true; curl_exec result enters json_decode directly or through unmodified local without splitting headers. Highlight decode call.
• Resolve builtin functions, classes, constants and methods; user-defined lookalikes are excluded. Follow only bounded local proof in one lexical scope.
• Emit one finding per violating operation, not per supporting evidence statement. When the proof is inconclusive, nothing is reported.

Exceptions (no report)

• Do not report unresolved or shadowed builtin names, unknown values, or incomplete receiver/type provenance. Unknown calls, aliases escaping, and intervening writes invalidate local proof. Similar code outside the stated detection contract is not a finding.
• Both standard suppression forms suppress this native ID.

Fix

None. Choosing a repair requires intent or additional runtime information.

PHP versions

Available throughout supported PHP 5.3–8.5 where the referenced builtin/extension is available. Respect syntax/version-specific receiver contracts; unavailable APIs are not this rule’s concern.

Configure

In custos.json:

{
  "rules": {
    "CurlHeadersIncludedInDecodedBody": {
      "enabled": false
    }
  }
}

Suppress

Before the statement or declaration (or the first statement of the file):

// @custos-ignore CurlHeadersIncludedInDecodedBody