orhun/rustypaste

Mitigating the effects of content discovery and fuzzer tools

Open

#28 opened on Oct 3, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (82 forks)auto 404
help wantedquestion

Repository metrics

Stars
 (1,183 stars)
PR merge metrics
 (PR metrics pending)

Description

Even though the names of uploaded files are random, fuzzer utilities can be used to discover content on the server.

Related questions are:

  • How can rustypaste be affected by such situation?
    • Need a demonstration of fuzzing with rustbuster or a similar tool.
  • Should there be any precautions for preventing this?
    • Implement blocking user-agents for common fuzzer tools (?)
  • Should we do anything?

I think it is an interesting topic and needs some brainstorming for improving security.

Contributor guide

Research direction
Investigate common fuzzer user agents and propose a list to block. Also consider rate limiting or CAPTCHA as alternatives. Test with a fuzzer tool like rustbuster.
Tech stack
rust
Domain
backendsecurity
Issue type
Security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45