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-cvss-scoringReport e compliance

reporting-cvss-scoring

⁨Assign a defensible severity to a finding — build the CVSS 3.1 vector from demonstrated impact and reconcile it with the program's own scale. Load on "what severity", "CVSS", "rate this bug", or before submitting a report. Signals: a confirmed finding needing a score, a program VRT/severity policy, ⁩

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-cvss-scoring

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

FirmaFirmato, ed25519
gBB/++i/xm…H4+b9pAA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto0c5fb627…3e4d237a
0c5fb62703c3…3ecc3e4d237a1 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-cvss-scoring@ee0e0c5

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

When it applies

A finding is reproduced and you must put a number on it — for a report, a dispute, or triage. A defensible score gets paid/prioritised fairly; an inflated one gets you closed as N/A and hurts your credibility.

Why it works

CVSS decomposes severity into metrics you justify one at a time from what you proved, not what's theoretically possible. Grounding each metric in demonstrated impact makes the score arguable and consistent, and mapping it to the program's scale turns it into the right payout/priority.

Method

  1. Score from demonstrated impact, metric by metric (CVSS 3.1 Base):
    • AV (Attack Vector): Network for a remote web bug, down to Physical.
    • AC/PR/UI: was it reliable (low complexity)? did it need auth (privileges)? did it need a victim action (user interaction)? Set from what your PoC actually required.
    • S (Scope): Changed if the bug crosses a trust/authority boundary (e.g. SSRF into internal services, sandbox escape) — a big multiplier, so justify it.
    • C/I/A: rate confidentiality/integrity/availability from what you demonstrated, not the worst imaginable.
  2. Produce the vector + score with the FIRST calculator (e.g. AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
  3. Reconcile with the program: map to Bugcrowd's VRT or the program's severity matrix — the program's policy is the ruling, CVSS is the starting point (tradecraft-bugbounty-platforms).
  4. Write the one-line justification for any contested metric (usually Scope and PR).

Gotchas

  • Don't claim Critical for a self-XSS, a bug needing implausible preconditions, or theoretical impact you didn't show — inflation gets you downgraded and distrusted.
  • Scope:Changed is the most abused metric — only when a real authority boundary is crossed.
  • A chain can score higher than any single bug; score the demonstrated chain (exploit-chaining).
  • CVSS ignores business context; the program's own scale (or a pentest's risk rating) may override.

Verify success

You have a CVSS vector whose every metric you can defend from your PoC, plus the program-scale severity it maps to — and it survives a sceptical triager.

References

FIRST CVSS 3.1 specification & calculator; Bugcrowd VRT; program severity policies.

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 2026ee0e0c50c5fb627Firmata–

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