Repository navigation
v3.12.1 — argument injection, file inclusion, and a chain the oracles can drive
The first release since v3.6.1, and it carries eight versions of work —
3.7.0 through 3.12.1 — plus the documentation and benchmark changes that
correctly took no version of their own.
What executed means has not changed, and that is the point of the release.
It still rests on a value RCEKit generated at random for that probe, which
reflection cannot produce, arriving through one of three channels: computed in
the response and absent from a payload-free control, an out-of-band callback
carrying a token only the target held, or a value the target stored that RCEKit
fetched back in a second request. Weaker signals keep their own tiers and are
never promoted into it. A run that could not test something still never reports
it as clean.
Two new methods
argv — argument injection into a program spawned with no shell (3.7.0).
This class sat in the README's excluded list until then, and the reason it moved
is the reason it is worth having: it is not a weaker case of command injection,
it is the case where the application did the correct thing. escapeshellarg
quotes the value exactly as documented, every separator arrives inert, and no
shell ever sees them — but that argument can still be read as an option, and
an option can name a command the program runs. Measured against vulhub
gitlist/CVE-2018-1000533: --methods reflected at --probe-depth full sends
37 probes and reports negative on all 37, while --methods argv reports
executed on the same endpoint in one probe. The oracle did not change; the
option names a command, and the command is the same arithmetic core.
include — a path the request names (3.11.0, reaching execution in 3.12.0).
The reads report file-read and stop there, because the evidence is a signature
RCEKit knew in advance rather than a value the target computed. Given
--include-write-url it also writes a computed one-liner through the sink and
fetches the file back, which reaches executed — or file-write where the file
is served verbatim. A wrapper carrying code (data://, php://input) is not
that route: both need allow_url_include, off by default since PHP 5.2, and the
measured target said so in its own words.
RCEKit now confirms through 11 methods under one --methods flag.
Two new kinds of reach
A chain is a delivery the detection engine drives (3.9.0). There were two
engines: --verify-chain carried the session machinery — login, a CSRF token
read from one response and spent in the next, a payload in an upload's content —
and --methods carried the oracles, the payload-free control and the tier
vocabulary, and they shared nothing. --verify-chain --methods now runs the real
oracles through the chain's steps, with a control that is a whole chain run of
its own. time and boolean are refused there by name: both read the shape of a
response series, which a chain's setup steps change for reasons that have nothing
to do with the sink.
--observe-trigger, because second-order detection has three acts (3.10.0).
Inject then read is enough for a payload the target renders on its own next page
load. It is not enough for one waiting to be run — a queue a worker drains, a
report generated on demand, a "run now" button — where polling reads a page that
will never move and the run reports negative about a sink that would execute
the moment anything asked. Measured against a target that queues the value on
POST /store and executes it only when /run is asked: the same probes report
negative=19 without the trigger and executed=19 with it.
One new tier
file-read (3.11.0) — arbitrary file read, CWE-22 / CWE-98, proven by
content absent from the payload-free control. A vulnerability on its own terms,
not a weaker RCE, and what it is worth depends on which paths you can reach.
Thirteen verdicts now, still never collapsed into each other.
Three places a verdict was stronger than its evidence
Each of these narrowed what RCEKit will claim. None of them narrowed what it
sends.
--verify-chain's in-band verdict wasexecutedon evidence the tier rule
forbids (3.8.0). The oracle there is a static signature —unamematched by
the wordLinuxappearing — and that path runs the chain once, with the
payload, so there is no control to difference it against. Both halves of what
executedrequires were missing. It reportsneeds-reviewnow. This is the
one upgrade note that matters; see below.- The observed channel awarded execution to whatever reached it (3.12.0).
The second-order channel assumed anything it could confirm proved execution,
which held while every method that could reach it did.includebroke that: a
file's content signature is in no payload and is not computed either, so a page
merely rendering the file reported second-order execution with nothing
executed. The tier travels with the probe shape now. include's traversal depths shared one filename and one product (3.12.0),
so they shared one read-back URL, and a depth whose own include failed
fetched the file an earlier depth had written and reported it as its own
execution. The run's verdict about the target stayed right; the map of which
shapes the sink accepts did not. Each probe draws its own operands and its own
filename.
Fixes worth naming
- A byte-order mark on a JSON response cost it its leaf channels and its
shape reading (3.7.1).json.loadsrejects a mark outright, so a marked body
yielded no leaf channels and the shape reading fell to its word-count fallback.
Both halves had to move together, because they are two readings of one body. - RCEKit died mid-report on a Windows console, and leaked its own path doing
it (3.12.1). Three strings carriedU+2192, which cp1252 cannot encode: two
report section closings andtime's evidence summary. The findings above the
closing line had already printed, so the run looked like it crashed while its
own verdicts scrolled past, and the traceback carried the module's absolute
path. Any run reporting a non-execution tier reached it, as did any redirected
pipe under a non-UTF-8 locale. CI runs on Linux under UTF-8 and had never seen
it.
Benchmark
17 cases, each with a negative control, and both halves must pass for a case
to pass. Seven are new since v3.6.1: boolean against mongo-express,
injection-point enumeration against Webmin, time as the subject rather than a
control, argv against GitList, and three for include — the read, and
execution against both a bare include sink and a framework loader that appends
its own extension.
That figure is a count of the suite, not of one run. python tests/bench/runner.py --all was last green at 3.0.1 — 10/10 in 55m48s — and
the seven added since were each run on their own. The benchmark runs on a
cadence, not on every change, and the README says which rows rest on which kind
of claim.
Documentation
The coverage ledger carries 16 rows, each stating the tier the bench
actually reached rather than the tier the method could reach in principle.
Quick start gained a scenario for the two sinks that are not shells — argv and
include both reach executed, and neither answers anything on the "what can
you observe" axis the other scenarios are organised by. The field guide gained a
section for an inclusion sink and a row for include in its method-choice table,
and that table, the contents lists and the environment lists are now pinned to
the code by tests, which is what they were missing.
Upgrade notes
Only one thing changes for a command line that worked before.
A --verify-chain run without --methods that previously printed
EXECUTED for an in-band match now prints a NEEDS-REVIEW candidate(s) section
instead. Nothing about the chain's delivery changed — the same steps,
substitutions and payloads go to the target — so a finding you reported from an
earlier run is not retracted by this. It is reclassified as something to confirm
rather than something confirmed.
To confirm it, reproduce the sink through --verify-url or -r with
--methods, where the oracles that rest on a computed value and a payload-free
control live — or run the same chain with --methods, which is new in 3.9.0
and carries those oracles through the chain's own steps. Exit status is
unaffected: that path returned 0 regardless of outcome before and still does.
Nothing else was removed or renamed. Python 3.8+, MIT, and still zero
third-party dependencies.
Verified at this tag
python -m unittest discover -s tests— 1203 tests, OK, run twice on a
checksummed tree: once under the native Windows console codec and once with the
parent locale forced to UTF-8, which is the locale CI has. Both green.python tools/embed_corpus.py --checkclean,python rcekit.py --doctorOK.- The bench figures above are stated as measured, with the date and build each
was measured against recorded intests/bench/README.md.