Skip to content

v3.19.0

Latest

Choose a tag to compare

@kabiri-labs kabiri-labs released this 19 Nov 10:50

v3.19.0 — a method for template sinks, and a channel for one-bit answers

The last published release was 3.15.0, so this release carries 3.16.0,
3.17.0, 3.18.0, 3.18.1, 3.18.2 and 3.19.0. CHANGELOG.md has the full entry
for each; what follows is what changed for someone running the tool.

New: --methods syntax (3.18.0)

A template sink answers malformed syntax differently from well-formed syntax,
and nothing is rendered either way — the shape of the response is the only
signal there is. syntax sends each delimiter form twice, once well-formed and
once with its closing delimiter removed, on two rounds of fresh operands, and
reports syntax-sink when the two rounds agree on what each half looked
like.

syntax-sink is a lead, not a finding. It says a parser is behind the value; it
does not say the input executed, and it is never promoted to confirmed. A
filter that refuses only the malformed half is reported inconclusive, and both
halves refused is blocked — neither reads as clean.

Verified against Flask 1.1.1 on Jinja2 in the bench suite, with a
class-attribution control.

New: boolean reads one bit of a JSON answer (3.19.0)

response_shape drops every scalar a document carries, which is what keeps a
request id or a timestamp from making two identical answers look different — and
which also made {"allowed":true} and {"allowed":false} the same shape. A
rules engine, a filter-expression evaluator and an authorisation endpoint all
have that shape, and the one method built for predicate sinks could not see
them.

The scalar channel reads those values back at identical JSON paths off the
series already fired
, so it costs no extra request unless it finds something,
and it runs only where the shape channel said nothing.

Its floors are measured rather than chosen: against a body carrying a scalar
that flips on its own, screening then confirming on four pairs gives 0 of
20000
false claims while still reading a real evaluator 20000 of 20000.
Four further guards exclude a confound structurally rather than by name. Because
four pairs per connective is the floor, this channel does not answer at
--probe-depth quick
and says so in the evidence rather than letting the run
read as clean. JSON only, deliberately: a path is a stable identity for "the
same value" and a plain-text body has none.

The ceiling is unchanged — evaluation-sink, a lead rather than a finding.

Fixes that change what a run reports

  • A refused request whose effect landed anyway now says so (3.16.0). A probe
    answered with a refusal whose side effect still happened was previously lost.
  • oob, lookup and deser findings carried no HTTP status (3.16.0).
  • A timeout the payload-free control did not share is no longer an error
    (3.17.0) — it is attributable, and attributable is a reading.
  • A write that landed while its own request hung was reported as error
    (3.17.0).
  • A syntax form its context cannot carry is no longer negative (3.18.1).
    A form whose broken half is closed by the context's own suffix is disclosed as
    not tested.
  • An observed endpoint behind a login no longer reads as one that was read
    (3.18.1), and a refused read no longer counts as a read (3.18.2).
  • A syntax pair voided by its own transport encoding is no longer judged
    (3.18.2).

Every one of these is the same rule in a different place: a run that could not
test something must not report it as clean.

Coverage

All 12 detection methods now have a bench case. python tests/bench/runner.py --all is green at 18/18 in 1h21m42s, every case with its negative control,
against real vulnerable software under Docker. tests/bench/README.md has the
table and the measurements.

Install

pip install rcekit==3.19.0

Python 3.8+, standard library only, no third-party dependencies.

RCEKit is for authorised testing only. See the responsible-use statement in the
README.