Repository navigation
RCEKit 3.0.0
RCEKit 3.0.0
Every verdict is now named for what the target did, never for how sure RCEKit is.
This release covers everything since v2.45.3: four patch releases that were never tagged, plus the tier rework that gives this one its major number.
Breaking: the verdict vocabulary
confirmed was the only verdict describing RCEKit's own confidence while every sibling described the target's behaviour. Next to it, a lookup-sink — proven on a callback carrying a token only that probe held — read as something unconfirmed.
And needs-review had four reporters, three of which had already measured their answer.
| Verdict | Was | What it says |
|---|---|---|
executed |
confirmed |
the target executed the input |
timing-sink |
needs-review |
the target honoured a delay RCEKit injected |
file-write |
needs-review |
a file stored at a path RCEKit chose, read back uninterpreted |
evaluation-sink |
needs-review |
an evaluator consumed the input; which one is not shown |
needs-review |
unchanged | deser's parser fingerprint — the one signal that really is a candidate |
write was the clearest case: its evidence line opened with the words ARBITRARY FILE WRITE confirmed under a status of needs-review. The tool's prose contradicted the tool's tier.
Nothing was promoted. executed rests on exactly the three channels it did before — a computed result in the response, an out-of-band callback, or a value the target stored that RCEKit fetched back — and none of the five weaker tiers has a path into it. time stays out in particular: a delay honoured is not necessarily a shell honouring it, since a sandbox implementing sleep answers the regression the same way.
What changed is the direction of the reporting error. Three proven findings were being under-reported.
Migration
--detect-json changes values, not keys. verdict, the keys of counts, each probe's verdict and observe_status take the new names above. A consumer keyed on "confirmed" must read "executed"; one keyed on "needs-review" should decide which of the four it actually meant.
No CLI flag, no JSON key, no template-schema field and no exit code changed.
No backward-compatible alias ships. Two accepted spellings for one field is a second source of truth, and the point of this release is that there is one.
Also in the collapsed verdict
needs-review now ranks last rather than second. Its old place was argued from "a suspected RCE outranks a proven non-RCE in triage", which held while time, boolean and write's uninterpreted file all reported there. What is left under it is a suspected deserialization, so ranking it above deserialization-sink put the guess above the proof of the same thing.
Full order: executed, timing-sink, file-write, evaluation-sink, deserialization-sink, lookup-sink, needs-review.
Three defects the benchmark found that no fixture could
These shipped as 2.45.4 through 2.45.7 and were never tagged.
- A compressed response body is a body the oracles cannot read. A target that gzipped its output read as clean for every method. Decompression is bounded, because compression is where a target chooses how much memory you spend.
- The
writeprobe carried whitespace, and some sinks tokenise before they interpret. Measured on RRDtool:<?= 7*6 ?>wrote no file,<?=7*6?>wrote 47 bytes. - The
writeproduct overflowed a 32-bit int. JSP and ASPX evaluatea*bas signed 32-bit while RCEKit computed it in Python, so the two disagreed and the run reportednegativeagainst a target that was fully exploitable — in 56% of runs on JVM and .NET targets. Operands are now bounded so the product cannot overflow.
Also fixed in that range: the deser shape differential answering from evidence it had not gathered, the pre-flight plan describing three payloads it no longer sent, and a negative evidence line describing a comparison it had not made.
Coverage you can re-run
The README's CVE table became a coverage ledger: 11 rows, every one with a bench case, each saying which build it was measured against and which negative control proves the result is not an over-eager scanner.
python tests/bench/runner.py --all — 9/9 cases, 55m50s, at 3.0.0, against the same vulhub builds. Every case's expected verdict changed in this release, so all nine ran; applying a rename to a stored result proves nothing about what the tool reports.
The two timing-sink controls carry the weight: on a Webmin 1.910 and an OpenTSDB 2.4.1 that are genuinely vulnerable, time reaches its own proven tier and still does not reach executed. That is the tier ceiling holding against real software rather than against a fixture.
Two of the new tiers are not in that run. file-write and evaluation-sink rest on unit tests only — the Tomcat write case reaches executed, and boolean has no bench case at all.
Notes
The four recordings in confirmation-gifs/ predate this release and show the old verdict names on screen. Only the words changed; what each run proves is the same. Their README says so rather than the repository claiming a coherence it does not have.
Python 3.8+, MIT, still zero third-party dependencies.
Full changelog: v2.45.3...v3.0.0