Repository navigation
ExeRadar 2026.42
Security
-
A filename can no longer run PowerShell. The catalog check (path B, Windows only)
put the path into the script as a single-quoted literal and doubled the ASCII quote,
and PowerShell closes that literal on U+2018, U+2019, U+201A and U+201B as well: a
file nameda’; <command>; ’b.exe, legal on NTFS, ran<command>with the user's
rights whenanalyze,batchorverifyreached it — one name in a downloaded folder
was enough forbatch. The path now travels in theEXERADAR_TARGETenvironment
variable and is never part of the script, so there is no escaping left to get wrong.
Checked against PowerShell's own parser, and on Windows by running it: a name that
carriesni pwnedis analysed as the catalog-signed file it is, and nopwnedappears. -
Strings out of the binary are printed, not obeyed. The console report passed
them to Rich as markup:http://evil.example/[/x]in a PE endedanalyzewith a
MarkupError, and a well-formed tag such as[link=…]was followed. Every value that
comes out of the file — its name, strings, section and DLL names, the signer, errors —
is escaped, inanalyzeand in thebatchtable. -
The Markdown report cannot carry HTML from the binary. A path such as
C:\y\`<img src=x onerror=alert(1)>`closed its code span and reached the ticket it
was pasted into as raw HTML; a section nameda|badded a column to the table. Code
spans now use a fence longer than any run of backticks inside them, pipes are escaped
in table cells, and free text — the file name, the signature sentence, library
evidence, notes — has& < > [ ]written as entities, which cannot turn back into
markup whatever precedes them. -
A forged certificate table no longer hides the file's strings. The range the
header declares for the certificate table was left out of string extraction even when
LIEF found no signature in it and even when it covered the sections: pointed at
0x400..EOF, it removed every URL, address and path from the report, and the
hardcoded_ipfinding with them. It is skipped now only when a signature was read
there, and only past the last section.
Fixed
-
A file whose path is not ASCII is analysed on Windows. LIEF opens a path through
the narrow API there, socaffè.exe, or anything underC:\Users\José, came back as
"not a PE file",verifyanswered 2 for a validly signed file, andbatchdropped it.
Python reads the bytes and LIEF parses them (pe.parse), on every platform. -
A countersignature time with an offset is converted to UTC.
+0200was printed as
local time with " UTC" after it, two hours off on the date that decides whether an
expired certificate is covered. A time with no zone at all says so instead of being
given one. -
A catalog signer whose Subject contains
|keeps its name. PowerShell's answer was
four fields joined by|, soO=Contoso|Fabrikamlost half of itself to the
timestamper. The script now answers in JSON. -
--outputinto a directory that is not there is refused before the scan, with exit
code 2, instead of aFileNotFoundErrortraceback after it; a write that fails anyway
(permissions, a full disk) is reported the same way. -
batchdoes not follow NTFS junctions.Path.rglobskips symlinks and follows
junctions, and one pointing back at its parent —mklink /J, no privilege needed —
listed the same PE 64 times.batch -owith nothing to report now says that no file
was written, instead of saying nothing. -
tlp.subjectcompares the first word, not a prefix: "TLP:REDACTED minutes" was
taken as already marked TLP:RED, and "TLP:AMBER+STRICT" as TLP:AMBER. -
first_teams.resolvedoes not choose between two exact matches. An organisation
can have more than one member team — a product PSIRT and a corporate CERT, with
different addresses and keys — and the first in the response was returned. Both are
now candidates, andpsirtexits 2. -
PyPI is published from a tag only, and after the suite.
publish.ymlcompared tag
and version for tags alone, so a dispatch from a branch published that branch; and it
waited for no test. Atestjob, without the publishing token, now comes first. -
The README examples say what the tool prints: "2 matching their signature" and
the signature sentences ofverify, which had changed since they were written. -
.gitattributeskeeps shell scripts LF. Withcore.autocrlf=truea Windows
checkout turnedrelease.shinto CRLF and bash stopped atset -euo pipefail. -
Five tests no longer assert the author's installed DLL versions (OpenSSL 3.5.8,
curl 8.13.0, pcre2 10.48): they failed on any machine that had updated Git for
Windows or Windows. The expected version is read from the library's own statement in
the same bytes; which library, and nothing else, is still asserted exactly. -
A dispatched rebuild now stands on the tag it was given.
docker.ymlcan be run by
hand with the tag of an already published release to rebuild it, and it checked out the
default branch — while the image is built from that checkout.The consequence was milder than it sounds, which is why it survived: the smoke test
compares the version inside the image against the tag and runs on apush: false
build, before the login and before anything is pushed, so a rebuild ofv2026.40from
amainholding 2026.41 failed rather than publishing the wrong code. What it meant is
that rebuilding an older release could not work at all, and failed with a version
mismatch that reads like a packaging problem rather than like a checkout standing in
the wrong place. patchradar had the same omission on 2026-10-04 with no comparison
behind it, where it would have taggedmain's code with an old release's number. -
The image is built on every push and pull request, not only when asked.
docker-build-check.ymlwas reachable by hand alone, so the only thing that built this
image automatically wasdocker.yml— on a tag, pushing as it went. The first attempt
at a build was the one that published it. Nothing stopped it from running on every
change: this image is built from the checkout with no version to resolve, unlike
apkradar's and mailradar's, whose build check has to be handed a published version
because their Dockerfiles install from the index. -
Three comments that said "the other four Radar install from PyPI". patchradar
stopped on 2026-10-04 and builds from the tag's source, as this one always has. Three
of four now, and the difference matters, because those comments are what somebody will
read when deciding what to do about the remaining ones.Four mutations hold the two new cases. One of them did not fail at first: the case read
a fixed 400-character window afteractions/checkout, which reaches into the step that
extracts the version and namesinputs.versionfor its own reasons — so a checkout
that ignored the input looked like one that used it. The window now ends where the step
ends.
Added
-
Findings in the
analyzereport. ARCHITECTURE.md section 7 separates facts from
findings, and the console and Markdown reports showed only the facts: a
signature_invalidof severity high reached the JSON and the count inbatchand
nobody readinganalyze. Both now end with the findings, title and severity first. -
"Provisions applied", as README and ARCHITECTURE.md section 5 describe.
law_checker.checkwas called by nothing, so no report carried a citation or the notes
that qualify them (the CRA applies from 11 December 2027; it binds a manufacturer).
analyzenow cites, in the console and in Markdown. The JSON is unchanged: it
carries the findings, not the citations. -
analyze --online, and offline by default.analyzecites from the local cache
in~/.exeradarand downloads nothing;--onlinedownloads the texts the findings
need and refreshes the cache. A provision the cache does not hold is cited without a
hash, and the run says so and suggests--online, instead of failing. A clean file
touches no network either way. -
The files the build is told to include are checked to be there. apkradar lost its
LICENSEout of the working tree on 2026-10-04 and the loss reachedmain: pyproject
names the file, sopython -m buildfailed withLicense file does not exist: LICENSE,
and the PyPI publish and the image went down with it. cookieradar lost its own a few
hours later, during a run of the suite. Neither suite noticed, because neither looked.What removes them is still not known, and these cases do not explain it. They stop it
reaching a commit, which is the part that can be fixed without knowing.The expectation is read out of the declarations rather than written down as
LICENSE,
because the five Radar do not declare it the same way: patchradar states its licence as
text and only its Dockerfile names the file, the other four name it in pyproject, and of
those apkradar and mailradar do not copy it into the image. So two cases — every file
pyproject names, and every path the Dockerfile copies — and between them each repository
is covered, three of them twice.Checked by moving the file aside in all five: it fails where it should and passes where
the declaration genuinely does not name it, and pointing pyproject at a file that is not
there fails too. -
A release script, which this repository never had. The other four Radar release
throughrelease.shorscripts/bump_version.py; here__version__was edited by
hand, committed, tagged and pushed. That is why the suite gate the other four were
given had nowhere to live: there was nothing to put it in. Ported from cookieradar,
where the script and its cases were written, with the version file and the product
name changed and nothing else.What it refuses: a version that is not
YYYY.count[.fix], a middle segment that
reads as a month, the version already in__init__.py, a branch other thanmain,
a dirty tree, a localmainout of step with the remote, and a tag that exists
either side. Then it bumps, runs the suite with the new version in place, and
commits only if it passes —publish.ymlalready checks that the tag matches
v$VERSION, so the two halves agree.23 cases hold it, and five mutations were checked against them: the gate removed,
the version check disabled, a dirty tree allowed, an existing tag no longer
stopping anything, and the push no longer atomic. All five fail.
Changed
-
law_checker.checktakesofflineinstead of**context. The extra keywords were
passed tofindings_ofandnotes_of, which accept none, so any of them ended in a
TypeErrorfrom inside the check. -
The catalog check has no branch left for an answer that is not JSON. Exit 0 from
the script is always one JSON object —[ordered]@{…} | ConvertTo-Json -Compressunder
$ErrorActionPreference='Stop'— and every failure (no such file, a directory, access
denied, a file in use) is a non-zero exit with nothing on stdout, which was already
turned away. Measured with the real PowerShell on 2026-10-07, on catalog-signed,
embedded-signed, unsigned, empty and text files, and held bytest_catalog_encoding.py.
Should it happen anyway, aValueErrorfromjson.loadsjoins theOSErrorand
SubprocessErrorpath: "I could not tell", never a traceback out ofanalyzeor
verify. -
The tests behind the fixes above ask real inputs, not mocks. PowerShell is the real
one on Windows; elsewhere it is its real replies, recorded in
tests/fixtures/powershell_catalog_replies.json, which a Windows case asks again and
compares, so a recording that stops being true fails rather than lingers. "No network
without--online" is a listener on 127.0.0.1 named as the proxy for every scheme, and
it hears--onlinereach europa.eu — which is what makes an empty list evidence. The
two exact matches in FIRST's directory are its real answer to?q=EY, "EY" and
"EY CSIRT", intests/fixtures/first_teams_ey.json. Againstmainbefore the fixes,
each converted test fails on the defect it protects.
Full Changelog: v2026.41...v2026.42