feat: AVE-2026-00072 -- MCP server bound to all interfaces (NeighborJack) - #129
Merged
chaksaray merged 2 commits intoAug 6, 2026
Merged
Conversation
…ack) Credit predictor2718's detailed cfgaudit gap breakdown on issue #68: MCP network posture was originally a topic label covering five distinct mechanisms. Drafted only the wildcard bind (CFG018), predictor2718's own recommendation for the single highest-value record: a server bound to 0.0.0.0/[::] is reachable by anyone on the LAN with no auth step, and the config difference from a safe deployment is a single token. Explicitly excludes four other real, distinct mechanisms from the same bucket, all future record candidates: wildcard CORS (CFG066, escalates to CVE-2026-33010 combined with disabled auth), deprecated SSE transport (CFG058), non-local proxy routing (CFG021), unredacted HTTP logging (CFG069, CVE-2026-42282/CVE-2026-41495). CWE-1327 (Binding to an Unrestricted IP Address) confirmed as a precise match. mitre_atlas left as a researched empty array: research confirms 'MCP server compromise as a pivot point' is an explicitly documented current gap in ATLAS coverage, not yet a defined technique. owasp_asi intentionally omitted, same discipline as AVE-2026-00061: this is a network access-control gap, not a fit for any of the ten agent-behavior-focused ASI categories.
…2-mcp-server-bound-all-interfaces # Conflicts: # CHANGELOG.md # README.md # dist/ave-records-latest.json # dist/ave-records-latest.manifest.json
chaksaray
deleted the
feat/AVE-2026-00072-mcp-server-bound-all-interfaces
branch
August 6, 2026 21:59
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
1 participant
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.
Summary
AVE-2026-00072: MCP server bound to all interfaces with no authentication, "NeighborJack" (MEDIUM, AIVSS 5.0). Second of three records drafted from predictor2718's detailed mechanism breakdown on issue #68.
Mechanism, and why exactly this one from the bucket
MCP network posture was originally a topic label covering five distinct mechanisms with no shared detection logic. This record covers only the wildcard bind (CFG018), predictor2718's own recommendation for the single highest-value record if one is drawn from the group: a server bound to
0.0.0.0/[::]is reachable by anyone on the LAN with no authentication step, and the config difference from a safe deployment is a single token.Explicitly excluded, all real, distinct future record candidates per predictor2718's own breakdown:
Framework mappings, researched not assumed
owasp_mcp: ["MCP07"](Insufficient Authentication & Authorization) verified against OWASP's own published category list.mitre_atlas: []: researched. Independent research confirms "MCP server compromise as a pivot point" is an explicitly documented current gap in ATLAS's own coverage, not yet a defined technique -- not a research shortfall, a genuine absence.owasp_asiintentionally omitted, same discipline already applied to AVE-2026-00061: this is a network access-control gap, not a fit for any of the ten agent-behavior-focused ASI categories.CWE-1327(Binding to an Unrestricted IP Address) confirmed as a precise match.AIVSS notes
AV:A(adjacent network) rather thanAV:N: exploitation requires LAN adjacency, not full internet reachability. MEDIUM despite a near-maximumcvss_base(8.7, full unauthenticated tool access to any LAN party) reflects AARF's narrow amplification profile.Validation
python3 scripts/validate_records.py: all 71 records valid.python3 scripts/check_fixtures.py: all 71 records have positive + negative fixtures.pytest tests/ -x -q: 284 passed.python3 scripts/validate_crosswalks.py: 4/4 crosswalks valid.node scripts/build-records.js: dist regenerated; frozen v1.1.0 snapshot untouched.Scope notes
No detection-rule PR in bawbel/scanner -- separate tracker. One more record from the same issue #68 breakdown to follow (telemetry redirect); a fourth (sandbox-config weakening) is explicitly held per predictor2718's own two flagged reasons.