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/code-review-rustWeb e bug bounty

code-review-rust

⁨Security review of Rust code — where a memory-safe language still has real bugs: `unsafe`, FFI, panics, and the usual injection/logic sinks. Load when reviewing Rust source/PR, on .rs / Cargo.toml in scope, or "review this Rust". Signals: Cargo.toml, unsafe blocks, extern "C", unwrap/expect, actix/a⁩

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

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/code-review-rust

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

FirmaFirmato, ed25519
Hdz+VCY8tv…VTNf7yCg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettod6db3498…84e8534a
d6db34984f71…fbc584e8534a1 file · ⁦1.8 KB⁩
ScansioneMedio1 segnalazione
  • injection.no_confirmationSKILL.md:55
Vedi la scansione completa
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/code-review/code-review-rust@ee0e0c5

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

When it applies

Reviewing Rust (a service, a CLI, a library). Safe Rust removes most memory bugs, so the review focuses on the places safety is opted out of, the ways Rust code still panics or mis-handles input, and ordinary injection/logic in web handlers.

Why it works

Rust's guarantees hold only outside unsafe and only for memory safety — they don't stop SQL built by string, a command run via a shell, a .unwrap() that panics on attacker input (DoS), or a logic error. Concentrating on those boundaries finds the real bugs efficiently.

Sinks & patterns (grep, then reason about the boundary)

  • unsafe blocks: every one is a manual proof obligation — raw pointer deref, get_unchecked, slice::from_raw_parts, mem::transmute, uninitialised memory. Check the invariant it assumes.
  • FFI: extern "C"/bindgen boundaries — lengths, lifetimes, and NUL handling across the C edge (the C side has none of Rust's guarantees; pair with code-review-cpp).
  • Panics as DoS: unwrap/expect/panic!/indexing v[i]/unreachable! on attacker-controlled input; integer as casts that truncate; arithmetic overflow (panics in debug, wraps in release — both can be bugs). Prefer ?/checked ops.
  • Injection: SQL via format! into a query instead of parameter binding (sqlx/diesel); std::process::Command with sh -c and concatenated input; Command arg vs shell form.
  • Path / SSRF: user paths joined without canonicalisation + prefix check; HTTP clients (reqwest) fetching user URLs.
  • Deserialization / web: serde into types from untrusted data (resource exhaustion, unexpected variants); actix/axum/rocket extractors bound to over-broad structs (mass assignment); missing auth middleware on state-changing routes.

Method

  1. Run cargo audit (known-vuln deps), cargo clippy, and semgrep; miri for unsafe UB where feasible.
  2. rg 'unsafe|unwrap\(\)|expect\(|transmute|Command::new|format!\(.*(SELECT|INSERT|UPDATE)' → review each.
  3. Justify every unsafe block's invariant; if you can't, that's a finding.
  4. Confirm exploitable injection/logic with the matching runtime skill.

Gotchas

  • Idiomatic Rust is genuinely safe — don't invent memory bugs in safe code; spend effort on unsafe, FFI, panics, deps, and logic.
  • Release-mode integer overflow wraps silently — a checked_*/saturating_* audit matters for size/index math.
  • cargo audit flags vulnerable crates you'd never see by reading — always run it.

References

Rustonomicon (unsafe); RustSec advisory DB / cargo-audit; Clippy lint set; Secure Rust Guidelines (ANSSI).

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

  1. MediaPrompt injection · injection.no_confirmationSKILL.md:55

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

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
code-review-rust | NotHoly Skills