Repository navigation
v3.15.0
RCEKit's verdicts were always careful. Reading them on a real terminal was not:
a run printed nothing for the minutes it was working, its own settings were
printed at the weight of a finding, nothing was coloured, and it never said what
it had decided. This release is almost entirely about that — and about one
vulnerability in which the target could forge a confirmation in the operator's
own terminal.
Four versions are folded into this tag (3.12.2, 3.13.0, 3.14.0, 3.15.0); none of
the intermediate ones were published.
Security
A target could forge a confirmation in your terminal. When a probe never
arrived, the delivery error became the reported detail — and
http.client.BadStatusLine carries the server's raw bytes, so a target replying
with an erase-line sequence followed by a forged EXECUTED row wiped the line
saying nothing had reached it and printed a confirmation in its place, for a run
that tested nothing.
The tier rule is the claim this project rests on, and this was that claim being
forged by the target it is supposed to describe. It needed no authentication and
no special position: any host you point RCEKit at could do it.
Every report row now renders through one escaping function, so what arrived
stays visible as \x1b instead of acting. Display only — --detect-json keeps
the bytes verbatim and is byte-identical to before.
Added
- A banner, two lines on stderr: the version, and the tier rule in the
README's own words. - A progress line for the minutes a run used to spend in silence —
elapsed time, method, carrier and probe count against the pre-flight's own
estimate. One self-erasing line on a terminal;--progress plainwrites a
line every 25 probes for a CI log;--progress noneturns it off. - A verdict line, the last thing every run prints:
[detect] VERDICT: negative -- the probes reached the target and found nothing - Colour, tied to the tier and nothing else.
executedbold red, the
proven-but-not-execution tiers yellow, a run that tested nothing bold yellow,
negativea neutral cyan. No green anywhere — green reads as "nothing
here", andnegativemeans the probes reached the target. - New flags:
--color {auto,always,never},--progress {auto,plain,none},
-q/--quiet.NO_COLOR,FORCE_COLORandTERM=dumbare honoured.
Fixed
- A redirected run printed nothing until it exited. stdout was block-
buffered and never flushed, so a run piped intotee, captured byscriptor
watched in CI was silent for its whole duration — measured at 50.2s to the
first line, now 0.2s. An operator watching a silent pipe cannot tell a working
run from a hung one. - The run's own configuration read as findings.
sink shell,sink shapes
and the shape descriptions wore the same[detect]tag the findings wear.
They are tagged[config]now. - RCEKit's log records went to stdout, duplicating the report with a
timestamp in front. They go to stderr. - Colour could not render on a Windows console where virtual-terminal
processing was off; RCEKit enables it for its own stdout, and where that
fails colour stays off rather than printing escape sequences at you. - The README said a run that reached nothing exits non-zero. It exits 0:
non-zero means a refusal to run. Branch on the verdict, not on$?—
--detect-jsoncarries it. - A payload containing a literal newline split its own finding row in two.
nothing-tested, the quietest way the tool can fail, was the one outcome that
never announced its verdict.
Upgrading
No flag was removed or renamed, no verdict was added, renamed or widened, and
--detect-json and the -o exports are byte-identical. Nothing in the
detection path changed.
If you parse stdout, four things moved:
INFO - ...log records are no longer there (they are on stderr).- Configuration lines are tagged
[config]instead of[detect]. - A
[detect] VERDICT: ...line is appended to every run. - stdout is line-buffered when redirected, so output arrives as it happens.
The banner and the progress line are on stderr and never touch stdout;
colour is never written to a redirected stdout. A run piped to a file produces
the same bytes it always did, plus the verdict line and the retagged
configuration.
Python 3.8 through 3.13. Still zero third-party dependencies.