Skip to content

v2.45.3 — a probe that cannot call back is not a probe

Choose a tag to compare

@kabiri-labs kabiri-labs released this 24 Sep 13:50
· 123 commits to main since this release

Patch release. One defect, reached by three different routes, all in how
--methods deser decides whether an out-of-band callback is possible.

Fixed

deser sent DNS gadgets that nothing could receive. Three configurations
produced the same failure — real requests to the target from which no callback
could follow by construction, and a verdict capped at needs-review without
saying why:

configuration before after
--methods deser --oob-host <name>, alone no listener started at all listener starts
--methods deser --oob-host <IP> gadget aimed at <token>.<IP>, which resolves nowhere gadget not built; the run says which method an address stranded
--methods deser --deser-formats php notice blamed the address; listener bound for nothing neither — php, dotnet and python_pickle ship no DNS gadget, so there was never a callback to lose

The root cause was one attribute answering two questions: whether a run should
stop when no --oob-host is named, and whether it needs a listener. Every
method but deser answers both the same way — its shape oracle proves
something with no listener at all, while its DNS gadget does call back.

deser now reaches deserialization-sink when run on its own, which is how
the documentation presents it.

Also

  • Two notices said "only the HTTP shapes are live" in runs that have no HTTP
    shape. They now say "only the shapes that need no DNS are live", true of
    oob's HTTP probes and deser's shape oracle alike.
  • lookup with an address no longer binds ports it cannot use. It built no
    probes with one either way.

Upgrading

No flags, verdicts or output schemas changed. The effect on a run is fewer
requests to the target in the configurations above, plus one notice naming any
method an address stranded and the tier that puts out of reach.

If you script against --methods deser, note that a run narrowed to php,
dotnet or python_pickle now correctly reports that it cannot reach
deserialization-sink, rather than appearing to try.

Note on this tag: the previous published tag is v2.35.1. Upgrading from
there spans 17 versions — see CHANGELOG.md for everything in
between.

Verified: 806 tests, full suite, on Python 3.8–3.13.