Repository navigation
Don't confirm CVE-2019-0211 from an Apache 403 page - #41
Draft
cursor[bot] wants to merge 1 commit into
Draft
cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
CVE-2019-0211 is a local prefork/worker scoreboard LPE. The verifier builtin treated GET /server-status 403 plus the word "Apache" (present in the default error-page footer) as probe confirmation, and fusion pinned it. Skip the CVE as not HTTP-testable, including AI re-plans. Co-authored-by: dmitryflynn <dmitryflynn@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug and impact
The CVE verifier builtin for CVE-2019-0211 (Apache prefork/worker scoreboard local privilege escalation, CVSS 7.8) sent
GET /server-statusand treated HTTP 403 plus the substringapacheas probe confirmation.A default Apache 403 page includes
<address>Apache/2.4.x (Ubuntu) Server at …</address>. Fusion maps a successful verifier signal toprobe_confirmedand the gate pins it as un-droppable. An--ai/--fullscan of Apache 2.4.17–2.4.38 therefore reported a confirmed LPE that was never tested.mod_status exposure is already a MEDIUM
service_proberfinding when the body actually contains scoreboard markers. It does not prove CVE-2019-0211.Trigger:
--ai/--fullwith an AI completer againstApache/2.4.29(or any 2.4.17–2.4.38 banner). NVD correlates CVE-2019-0211. VerifierGET /server-status→ default 403 footer containingApache→ fusion-confirmed.Root cause
The builtin used
expected_status: [200, 403]andexpected_body_patterns: ["apache", "server-status"]. 403 is access denied, not evidence of the scoreboard race. The wordApacheis on every stock error page.Fix
generate_plans_for_cvesandreverify_with_contextso an AI completer cannot reinvent the same probe.Validation
python3 -m pytest test_verifier_sanitize.py test_fusion.py test_fusion_engine_bridge.py test_gate_version_cap.py -q— 60 passed.python3 -m bandit -r src/verifier/planner.py --severity-level high— no high issues.New case: default Apache 403 on
/server-statusno longer yields a plan (builtin or AI); a leftover plan against that 403 still matches, which is why generation is skipped.