Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
noorqureshi/code-review-rustWeb y 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 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 23 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

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

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
Hdz+VCY8tv…VTNf7yCg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paqueted6db3498…84e8534a
d6db34984f71…fbc584e8534a1 archivo · ⁦1.8 KB⁩
EscaneoMedio1 hallazgo
  • injection.no_confirmationSKILL.md:55
Ver el escaneo completo
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/code-review/code-review-rust@ee0e0c5

Esta entrada todavía no está escrita en tu idioma, así que aparece en 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).

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

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

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.10.14-ee0e0c513 nov 2026ee0e0c5d6db3498Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login