Skip to content

Don't confirm Shellshock CRITICAL from header reflection - #39

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/critical-bug-management-2590
Draft

cursor[bot] wants to merge 1 commit into
mainfrom
cursor/critical-bug-management-2590

Conversation

@cursor

@cursor cursor Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Bug and impact

probe_shellshock confirmed CVE-2014-6271 CRITICAL (fusion-pinned, un-droppable) whenever the HTTP response contained the string NETLOGIC_SHELLSHOCK_CONFIRMED.

That marker was also sent in User-Agent, Referer, and Cookie. Any CGI that dumps the request environment — including Apache's stock /cgi-bin/printenv, which is one of the paths this probe hits — echoes the marker without bash executing anything. Fusion then pins it as confirmed RCE.

Trigger: scan an HTTP host that has Apache printenv (or any UA-reflecting error/debug page) on a standard web port. No vulnerable bash required.

Root cause

Confirmation searched the raw response for a token that was present in the request headers. Reflection and execution were indistinguishable.

Fix

Inject echo NETLOGIC_$((7*191*13)) and confirm only the evaluated token NETLOGIC_17381, which header reflection cannot produce. A real bash CGI still emits the token (true positive even if it also dumps env).

Validation

  • test_probers.py: 45 passed, including new cases for printenv-style reflection (no finding) and execution+env dump (still confirms).
  • Live monkeypatched probe: printenv reflection → None; bash evaluates to NETLOGIC_17381; execution → CVE-2014-6271 CRITICAL with fusion pinned=True.
Open in Web View Automation 

probe_shellshock treated any response containing the injected User-Agent
marker as CVE-2014-6271 RCE. Apache printenv and other CGIs that echo
request headers produced a fusion-pinned CRITICAL without bash executing
the payload. Confirm only the evaluated arithmetic token, which reflection
cannot produce.

Co-authored-by: dmitryflynn <dmitryflynn@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant