Skip to content

v2.34.1 — seven methods, seven verdicts

Choose a tag to compare

@kabiri-labs kabiri-labs released this 18 Aug 07:28
· 176 commits to main since this release

Everything since v2.23.3 — eleven releases, two new detection methods, eighteen
new flags, and a detection engine that is considerably harder to fool into
reporting a clean negative.

The tagline changed too, because the old one overclaimed:

confirmed means the target executed the input. negative means the probes reached it.

Two new detection methods

--methods goes from five to seven.

Method Confirms Tier it can reach
write An upload or write primitive proven to be RCE by executing what it wrote — PUT-a-JSP, unchecked upload (CWE-434) confirmed, or needs-review for a write that is served but not interpreted
deser That the endpoint deserializes attacker data — via a non-executing DNS gadget or an error-shape differential deserialization-sink, never RCE

deser ships a URLDNS builder written against OpenJDK's own ObjectOutputStream
byte layout and verified on OpenJDK 21: the stream deserializes to
HashMap{http://<host>/=rk} and issues a DNS query for <host>, referencing no
class outside java.util/java.net — so the callback proves the object graph
was reconstructed and nothing more.

Sinks the engine can now reach

  • Windows cmd.exe and PowerShell (--sink-env). The shell dialect was
    inferred from the corpus environment alone, so every Windows carrier took the
    cmd core — including the one whose context is literally named powershell.
    Every shell method now has a PowerShell shape, each validated against pwsh 7.4.
  • Second-order execution (--observe-url, --observe-request). The payload
    lands on one request and runs on another: stored SSTI rendered on a profile
    page, a payload written to a log a template engine later renders, a queued job.
    Differenced against a snapshot of that endpoint taken before any probe was
    sent.
  • Query-language bridges (--bridges). COPY … FROM PROGRAM,
    xp_cmdshell, expect://. A carrier, not an oracle: it wraps the command the
    methods already build, so the same tier guarantees apply through it.
  • Any read-back path (--file-write-path, --file-read-url). file needed
    a writable web root; it now works through an LFI parameter, a download or
    export handler, a /tmp-backed preview. Measured against a target with a
    download handler and nothing serving the write directory: the web-root form
    confirms 0, the general form confirms 7.
  • Injection-point enumeration (-p all, --auto-params). Query, JSON
    leaves, form fields, cookies, headers and path segments, each encoded for
    where it lands, with the probe cost printed before anything fires.
  • The whole response as a confirmation channel — body, application headers,
    cookie values, the redirect target, the HTTP reason phrase, and each leaf of a
    JSON error envelope. The control differential is applied to every channel too.
  • The sink-shape ladder (--sink-shape) — quoted sinks, whole-command
    sinks, and $( )/backtick substitution reaching a quoted value without
    closing the quote.
  • Sandbox-resistant eval carriers (--eval-engines) for Freemarker,
    Velocity and Thymeleaf, whose output and syntax quirks made a genuinely
    evaluating target read as negative.

The verdict model

A new tier, deserialization-sink: proven, but about a different property.
It sits below both RCE tiers and can never become confirmed.

And the half that matters more than it looks — a run that tested nothing is
never reported as clean.
error and nothing-tested are first-class verdicts,
the run exits non-zero, and RCEKit says which happened and why.

Fixed — mostly one defect wearing different clothes

Every one of these was found while building the features above, and most belong
to the same family: a run that tested nothing reporting as "not vulnerable."

  • A deeply nested JSON body raised RecursionError and turned all 46 probes
    of a default reflected run into error: request never reached the target —
    an evasion vector.
  • The raw rung reached only reflected. Under --sink-shape raw, file,
    time and oob built zero probes, and an aggregate method with no samples
    returned negative.
  • A JSON key containing a . produced two candidates with the same address, and
    the literal key was never probed at all.
  • The read-back fetch went out without the run's credentials, so an
    authenticated download handler reported confirmed=0 on a target where the
    write had executed on every probe. Credentials now travel same-origin only.
  • --observe-timeout 0 is falsy, so or 60.0 turned a deliberate no-wait read
    into a full minute of polling a dead endpoint.
  • The observed channel was polled only after the whole batch, which confirms
    nothing on a store that overwrites — the shape that oracle most exists for.
  • Two benchmark controls passed while measuring nothing: one copied the
    vulnerable invocation, the other accepted error/nothing-tested as a pass.
  • The Postgres bridge without a leading DROP TABLE IF EXISTS aborted its own
    second statement, so a target that was executing read as no delay.
  • An aggregate method's result carried no cleanup line, so a stateful bridge on
    the one oracle that reliably proves a query-language sink never said how to
    clean up after itself.

Upgrading

No breaking changes — no flag was removed and nothing changed meaning. Worth
re-checking if you script around RCEKit:

  • --detect-json gained deserialization-sink as a possible verdict, and an
    observe_status key on every probe.
  • A default run sends a different probe mix: the sink-shape ladder adds the
    quoted, substitution and raw shapes; cmd.exe no longer gets the sq/dq/
    subshell carriers it could never execute; dotnet gains cmd and PowerShell
    carriers.
  • needs-review findings now print their cleanup line, and aggregate methods
    (time) carry one too.
  • PowerShell's separator sweep carries no pipe — measured: cmd | <cmdlet> is a
    parameter-binding error, not a fresh command with stdin attached.
  • The corpus grew three declarative sections — eval_carriers, bridges and
    deser_probes — so a custom --template-file from 2.23.x still loads, but
    will not carry the new coverage until those sections are added.

Verification

506 tests, standard library only, Python 3.8 – 3.13. tests/bench/ adds a
vulhub benchmark harness in which a negative control is a required key, not an
optional extra.

Full changelog: v2.23.3...v2.34.1