bug-bounty-report-writing
Write bug bounty reports that get triaged quickly and rated accurately — clear impact statements, minimal reproduction steps, and professional tone. Use before submitting any vulnerability report.
v2026.8.26-b2b6b523 installazioni+3 in 7 giorni0 Stellesincronizzato 19 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install securityskills/bug-bounty-report-writingScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto4b1b27c9…fd0d15ae
4b1b27c9575f…0a5ffd0d15ae1 file · 1.1 KBScansioneMedio1 segnalazione
- Nessuna licenza trovata
Sorgentegithub.com/securityskills/skills/tree/main/bug-bounty/bug-bounty-report-writing@b2b6b52
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
Turn findings into reports that triagers accept quickly and rate fairly.
Report Structure
- Title — vulnerability class + affected asset.
Stored XSS in ticket comment field on support.example.com - Severity & CVSS — your suggested rating with vector string
- Summary — 2–3 sentences: what, where, impact
- Steps to Reproduce — numbered, copy-pasteable, no assumptions
- Impact — what an attacker gains, concretely
- Supporting Material — HTTP requests/responses, screenshots with sensitive data redacted
- Remediation — specific fix recommendation
Rules
- One vulnerability per report. Chains go in one report only when each step is meaningless alone.
- Impact must be demonstrated or rigorously argued, not speculated. "Could lead to RCE" without a path gets downgraded.
- Redact personal data in evidence. Blur user PII; never include other users' data you accessed — report the access, delete the data.
- No markdown-breaking formatting in pasted logs; use fenced code blocks.
- Write for a triager seeing the asset for the first time.
Common Downgrade Causes to Avoid
- Self-XSS or XSS requiring victim-installed software presented as high severity
- Missing
Content-Security-Policyor verbose headers with no demonstrated exploit - Theoretical IDOR without showing two distinct accounts affected
- Automated scanner output pasted without manual verification
After Submission
- Respond to triager questions within the program's SLA
- Request re-review only after substantive new information
- Do not disclose publicly until the program's disclosure policy allows
File di questa versione
- SKILL.md1.9 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaLicenza · Nessuna licenza trovata
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.8.26-b2b6b52 | 13 nov 2026 | b2b6b52 | 4b1b27c9 | Firmata | – |
Altro da securityskills
Tutto da questo editoreAltro in Report e compliance
Vai alla categoria- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login