Summary
A path traversal vulnerability in AsyncFuncAI deepwiki-open allows unauthenticated remote attackers to request directory listings for arbitrary filesystem paths through the local-repository structure endpoint.
When authentication is disabled and the endpoint accepts unrestricted absolute paths, an attacker may enumerate sensitive directories on the host.
Affected context
The vulnerability occurs in deployments of AsyncFuncAI deepwiki-open where the local-repository structure endpoint is network-accessible and authentication is disabled or not otherwise enforced. Risk is increased when the endpoint accepts absolute filesystem paths without restricting requests to an approved repository root.
Exploit preconditions
- Attack surface: The local-repository structure HTTP endpoint
- Required access: Network access to the endpoint; authentication is not required when the default unauthenticated mode remains enabled
- Trigger point: A request containing an absolute filesystem path
- Why exploitation is possible: The endpoint returns directory listings without sufficiently constraining the requested path to an authorized repository location
Why this happens
The underlying issue is improper restriction of user-controlled filesystem paths, mapping to CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
The endpoint uses a caller-supplied path to select a filesystem location but does not reliably enforce a permitted directory boundary. Accepting absolute paths without canonicalization, authorization, and containment checks allows requests to escape the intended repository scope and disclose directory metadata.
Potential impact
- An attacker may enumerate sensitive directories on the host
- Directory names may reveal application structure, deployment details, or operational data
- Exposed paths could assist follow-on attacks against local services or configuration files
- The vulnerability could increase the risk of broader information disclosure when combined with other weaknesses
General mitigation guidance
Mitigation generally focuses on reducing filesystem path trust and enforcing an explicit repository boundary.
Common defensive patterns include:
- Resolve requested paths canonically and verify that they remain within an approved repository root
- Prefer repository identifiers or server-side path mappings over client-supplied absolute paths
- Reject absolute paths, traversal components, and symbolic-link escapes where they are not required
- Require authentication and authorization before exposing repository structure
- Apply least-privilege filesystem permissions to the service account
- Return only the minimum directory metadata needed by the application
- Use secure-by-default authentication and deny access when authorization configuration is absent or invalid
How teams detect issues like this
Organizations can detect this class of issue through:
- Static analysis for filesystem APIs receiving HTTP parameters without canonicalization and boundary checks
- Code review for direct use of absolute paths, traversal segments, or unrestricted path joins
- Dynamic tests that request paths outside the intended repository root, including normalized and symbolic-link variants
- API policy checks requiring authentication and authorization for filesystem-backed endpoints
- Monitoring for unusual directory-enumeration requests and access to paths outside configured repository locations
Automated security scanning and code review tools may help identify path-handling and missing-access-control patterns.

