Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/reporting-bug-bounty-writeupReport e compliance

reporting-bug-bounty-writeup

⁨Turn a confirmed finding into a triage-friendly bug-bounty report (HackerOne/Bugcrowd) with correct severity and clean evidence. Load when a bug is validated and needs submitting, on "write the report", "CVSS", "severity", or before disclosure. Signals: a reproduced finding, a program's VRT/severity⁩

v2026.10.14-ee0e0c53 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/reporting-bug-bounty-writeup

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
gI8PyNP866…67P9qxCQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto89ce9d9a…707f78e1
89ce9d9a843c…207f707f78e11 file · ⁦1.5 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/reporting/reporting-bug-bounty-writeup@ee0e0c5

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

When it governs

After you've reproduced a finding and confirmed it's in scope. A great report gets triaged fast and paid fairly; a sloppy one gets closed as informational regardless of the bug.

Structure (what triagers want)

  1. Title — [Vuln class] on <asset> allows <impact> (specific, no hype).
  2. Summary — 2–3 sentences: what, where, why it matters.
  3. Severity — CVSS 3.1 vector + score, reconciled with the program's VRT/policy. Justify the Impact metrics from demonstrated impact, not theoretical maximum.
  4. Steps to reproduce — numbered, copy-pasteable, from a clean session. Include exact requests (method, URL, headers, body) and account roles used.
  5. Proof — minimal PoC that proves impact (a screenshot with the URL bar, a request/response pair, a short video). document.domain for XSS; sts get-caller-identity for cloud, etc.
  6. Impact — the realistic business consequence, tied to what you proved.
  7. Remediation — the correct fix (allowlist, output encoding, object-level authz…).

Evidence hygiene (do before you submit)

  • Redact real PII/secrets — prove the class with your own/test data, not customer records.
  • Scrub cookies/tokens/authorization headers from pasted requests.
  • Deduplicate: one report per root cause; note additional affected endpoints inside it.
  • Stay within RoE: no data hoarding, no lateral movement beyond proof, no DoS.

Severity gotchas

  • Don't claim Critical for a self-XSS or a bug needing implausible preconditions — inflated severity gets you closed as N/A.
  • Chain low bugs into a higher-impact narrative when they genuinely combine (and show the chain).
  • Map to the program's own scale; CVSS is the starting point, the program policy is the ruling.

Verify before sending

A colleague (or you, from a fresh session) can reproduce it from your steps alone, the PoC proves impact, and nothing sensitive is exposed in the report.

References

FIRST CVSS 3.1 calculator; Bugcrowd VRT; HackerOne report best-practices.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.10.14-ee0e0c513 nov 2026ee0e0c589ce9d9aFirmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login