MozillaSecurity / MozillaSecurity/FuzzManager

[CrashManager] Implement size limits for crashes submitted

Open
#238 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

crashmanager enhancement help wanted
Dominant language
Python
Stars
208
Forks
48
Avg merge
23h 5m
Merged PRs (30d)
2

Description

Size limits should apply to

  • stdout (default 1 MB)
  • stderr (default 1 MB)
  • crashdata (default 1 MB)
  • testcase (default 10 MB, Bugzilla default)

These limits are security/stability limits and should be hard-enforced (server will return an error code, client will raise). They should be configurable in server/server/settings.py.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with server/server/settings.py to understand the configuration structure, then locate the CrashManager submission paths for stdout, stderr, crashdata, and testcase. Implement the stated default limits as configurable settings, enforce them server-side, and verify that oversized submissions return an error code and cause the client to raise.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.