GitHub Bounties💵 paid workby fennhelloworldbuilt with AIscored by google/gemini-2.5-flash

SecureBananaLabs/bug-bounty: Search endpoint has no input validation or length limit on query

Visit project ↗Discussion ↗

💵 Funded work— see “Deliver it” below for how to respond.

Opportunity

AI-buildable

Traction

Creativity

The take

effort: ~weekend

This is a bug bounty issue for a missing input validation and length limit on a search query endpoint in a Node.js API. The task is to implement trimming, length limiting (e.g., 200 characters), and sanitization for the `req.query.q` parameter before it is passed to the search service. This is a straightforward fix for a known vulnerability.

Demand & gap

Painkillerdemand 88

Demand

Will. to pay

Gap

Buyer

Developers

The gap in what exists: This specific bug requires a direct fix, and the bounty offers a paid opportunity for a developer to address it.
Wedge to win: The wedge is directly delivering the fix for the stated bounty, appealing to the issue author looking to resolve a vulnerability quickly.
Reputation value (worth doing free for proof) — 70/100: Successfully fixing a bounty issue on a public GitHub repository provides concrete proof of security-conscious development skills and practical problem-solving, enhancing the operator's portfolio for future dev-tool or freelance clients.
Likely monetization: bounty payment

Deliver it

A starter prompt for Claude Code, what you'll need, and how to reach them.

You are an expert Node.js and security developer. The task is to fix a bug bounty issue in the `SecureBananaLabs/bug-bounty` repository. The `GET /api/search` endpoint passes `req.query.q` directly to the search service without validation. Implement input validation for the `req.query.q` parameter in `apps/api/src/controllers/searchController.js`. Specifically, you need to: 1. Trim whitespace from the `req.query.q` string. 2. Limit its length to a maximum of 200 characters. 3. Sanitize the string to prevent common injection attacks (e.g., using `dompurify` or a similar library, or basic regex for alphanumeric and safe symbols). Use a simple, robust sanitization approach suitable for a search query. The existing code is `export async function search(req, res) { return ok(res, await globalSearch(req.query.q ?? "")); }`. Fork the repository, create a new branch, apply the changes, add relevant unit tests to verify the trimming, length limit, and sanitization, and prepare a pull request. Assume the project uses standard Node.js/Express conventions. Focus on a clear, concise, and secure implementation. Define the `ok` helper as a simple `res.status(200).json({ success: true, results: data });` for local testing if not defined.

Prerequisites — cost & what to learn

How you'd build it

1Fork the SecureBananaLabs/bug-bounty repository.
2Create a new branch for the fix based on the issue description.
3Implement input validation (trimming, length limiting to ~200 chars, sanitization) for `req.query.q` in `apps/api/src/controllers/searchController.js`.
4Add unit tests to cover the new validation logic.
5Create a pull request with the fix, referencing the bounty issue.

Risks & moats

Understanding the existing codebase and test setup might take a small amount of time.
Ensuring sanitization is robust without breaking legitimate search queries.
The bounty might be claimed by someone else quickly if not acted upon fast.

Market it to your portfolio

fit 40

Forge KitRepo Gardener

This project is a good fit for developers interested in secure coding practices. The operator could highlight how 'forge-kit' or 'repo-gardener' could help maintain code quality and security by automating checks for such issues, appealing to teams or solo operators working on similar web services.

Original context

Bounty (amount on the issue). ## Bug: Missing Input Validation on Search Query **Description:** The `GET /api/search` endpoint passes `req.query.q` directly to the search service without any validation or length limits. An attacker could send extremely long query strings to consume server resources. **File:** `apps/api/src/controllers/searchController.js` **Current code:** ```js export async function search(req, res) { return ok(res, await globalSearch(req.query.q ?? "")); } ``` **Expected behavior:** The search query should be validated — trimmed, limited in length (e.g., 200 chars), and sanitized. **Impact:** Low-Medium — potential DoS via overly long query strings. This issue is limited only to the creator of this issue. This means that only the issue author can attempt to solve this issue. If you would like to work on it, please create another issue with the same contents and refer to issue #743 for more information.