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-javaWeb e bug bounty

code-review-java

⁨Security review of Java code — dangerous sinks and Spring pitfalls. Load when reviewing a Java/ Spring codebase/PR, on .java source in scope, or "review this Java". Signals: pom.xml/build.gradle, Spring/Spring Boot, ObjectInputStream, XML parsers, Runtime.exec, JNDI/lookups.⁩

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-java

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

FirmaFirmato, ed25519
LE1qhduZuW…N+IkLnCQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto83c4cbec…e02a3fe1
83c4cbec4dd7…6628e02a3fe11 file · ⁦1.7 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/code-review/code-review-java@ee0e0c5

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

When it applies

Reviewing Java source, most often a Spring/Spring Boot service. Java's biggest hitters are deserialization, XXE-by-default, and expression-language injection — all high impact and all grep-able.

Why it works

Several Java APIs are unsafe by default (XML parsers resolve external entities; ObjectInputStream instantiates arbitrary classes) and frameworks expose powerful expression languages (SpEL/OGNL) that turn a string into code. Tracing the source to a request parameter or message body confirms reach.

Sinks & patterns (grep, then trace to user input)

  • Deserialization: ObjectInputStream.readObject, Jackson enableDefaultTyping/polymorphic types, XMLDecoder, SnakeYAML new Yaml().load, unsafe readValue with type info → RCE gadgets.
  • XXE: DocumentBuilderFactory, SAXParser, XMLInputFactory, TransformerFactory without setFeature(disallow-doctype)/secure-processing.
  • Command exec: Runtime.getRuntime().exec, ProcessBuilder with concatenated input.
  • Expression injection: SpEL (SpelExpressionParser, @Value("#{...}") on input), OGNL (Struts), MVEL; template engines with unescaped output.
  • SQL/HQL: Statement/string-built queries, createQuery with concatenation.
  • SSRF: URL.openConnection, RestTemplate, HttpClient, WebClient on user URLs.
  • JNDI: InitialContext.lookup, log4j-style ${jndi:...} (Log4Shell) reachable from input.

Framework specifics

  • Spring: mass assignment via @ModelAttribute/DataBinder (missing setAllowedFields), exposed/unsecured Actuator endpoints, @RequestMapping path traversal, permit-all misconfig in SecurityFilterChain, SpEL in @PreAuthorize.
  • Struts/older MVC: OGNL injection (S2-* CVEs).

Method

  1. rg for the sinks; trace to controller params, headers, or message consumers.
  2. Check XML parser factory configuration everywhere XML is read.
  3. Review the Spring Security config for accidental permitAll()/disabled CSRF on state-changing routes.
  4. Confirm with web-deserialization, web-xxe, web-ssrf, or web-command-injection.

Gotchas

  • Jackson is safe unless default/polymorphic typing is enabled — check for it specifically.
  • find-sec-bugs/CodeQL surface candidates; you still must prove input reaches the sink.
  • Log4Shell-style lookups can fire from headers (User-Agent, X-Forwarded-For), not just body.

References

OWASP Deserialization & XXE cheat sheets; SpEL/OGNL injection research; find-sec-bugs rules.

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

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