Repository navigation
Don't confirm CVE-2024-38476/38477 from an Apache 403 page - #43
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
A default or shared-hosting 403 that echoes .htaccess/.htpasswd is not evidence of substitution encoding or a mod_proxy crash. Drop the builtins and skip AI re-planning so fusion cannot pin a false CRITICAL. 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 builtins for CVE-2024-38476 (Apache substitution encoding / source disclosure) and CVE-2024-38477 (mod_proxy NULL dereference DoS) sent
GET /.htaccessandGET /.htpasswdand treated HTTP 403 plus the substringhtaccess/htpasswdas probe confirmation.A default Apache 2.4.6 / 2.4.29 403 page includes
You don't have permission to access /.htaccess on this server.Shared-hosting Apache also emitsServer unable to read htaccess file, denying access to be safe. Fusion maps a successful verifier signal toprobe_confirmedand the gate pins it as un-droppable. An--ai/--fullscan of those Apache 2.4.x banners therefore reported a confirmed CRITICAL that was never tested.A 403 on
.ht*is the secure default (<Files ".ht*"> Require all denied</Files>). It does not prove substitution encoding or a mod_proxy crash.Trigger:
--ai/--fullagainstApache/2.4.29(Ubuntu 18.04) orApache/2.4.6(CentOS 7 / RHEL 7), both in the CVE-2024-38476 affected range. NVD correlates the CVE. VerifierGET /.htaccess→ 403 body containinghtaccess→ fusion-confirmed CRITICAL. Same path for CVE-2024-38477 via/.htpasswd.Distinct from #41 (
CVE-2019-0211/server-status+apachefooter) and #42 (CVE-2021-39275/ encodedwin.ini+fonts).Root cause
The builtins used
expected_status: [200, 403]andexpected_body_patterns: ["htaccess"]/["htpasswd"]. 403 is access denied, not evidence of either bug. The requested filename is echoed on stock early-2.4 error pages and on common shared-host 403 text.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— 61 passed.python3 -m bandit -r src/verifier/planner.py --severity-level high— no high issues.New cases: default Apache 403 on
/.htaccess//.htpasswdno longer yields a plan (builtin or AI); a leftover plan against that 403 still matches, which is why generation is skipped.