Skip to content

[Security][Critical] Spider endpoints completely unauthenticated — POST /spider/* #30

@bahdcoder

Description

@bahdcoder

Vulnerability

All Spider endpoints (/spider/crawl, /spider/search, /spider/links, /spider/screenshot, /spider/transform) have no authentication middleware applied. The route registration explicitly omits TokenAuth with a TODO comment acknowledging this is temporary.

Impact

  • Any unauthenticated user can invoke Spider.cloud API calls through the server, using the platform's paid API quota without authorization.
  • The server becomes an open proxy for web crawling, search, screenshots, and link extraction.
  • Attackers can enumerate and crawl arbitrary URLs, take screenshots of internal services, and search for content at no cost to themselves.
  • No rate limiting is applied to these routes, enabling high-volume abuse.

Endpoint

  • POST /spider/crawl — parameter url is passed to Spider.cloud without auth
  • POST /spider/search — parameter search is passed to Spider.cloud without auth
  • POST /spider/links — parameter url is passed to Spider.cloud without auth
  • POST /spider/screenshot — parameter url is passed to Spider.cloud without auth
  • POST /spider/transform — parameter data is passed to Spider.cloud without auth

Recommendation

Apply TokenAuth middleware to the /spider route group. The TODO comment indicates this was planned but deferred. Add rate limiting to prevent abuse even for authenticated users.

Metadata

Metadata

Assignees

No one assigned

    Labels

    authAuthentication vulnerabilitysecuritySecurity vulnerability or concernseverity:criticalCritical severity

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions