Skip to content

ExeRadar 2026.42

Choose a tag to compare

@github-actions github-actions released this 08 Oct 15:22
· 36 commits to main since this release
v2026.42
bd5396d

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 named a’; <command>; ’b.exe, legal on NTFS, ran <command> with the user's
    rights when analyze, batch or verify reached it — one name in a downloaded folder
    was enough for batch. The path now travels in the EXERADAR_TARGET environment
    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
    carries ni pwned is analysed as the catalog-signed file it is, and no pwned appears.

  • 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 ended analyze with 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, in analyze and in the batch table.

  • 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 named a|b added 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_ip finding 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, so caffè.exe, or anything under C:\Users\José, came back as
    "not a PE file", verify answered 2 for a validly signed file, and batch dropped it.
    Python reads the bytes and LIEF parses them (pe.parse), on every platform.

  • A countersignature time with an offset is converted to UTC. +0200 was 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 |, so O=Contoso|Fabrikam lost half of itself to the
    timestamper. The script now answers in JSON.

  • --output into a directory that is not there is refused before the scan, with exit
    code 2, instead of a FileNotFoundError traceback after it; a write that fails anyway
    (permissions, a full disk) is reported the same way.

  • batch does not follow NTFS junctions. Path.rglob skips symlinks and follows
    junctions, and one pointing back at its parent — mklink /J, no privilege needed —
    listed the same PE 64 times. batch -o with nothing to report now says that no file
    was written, instead of saying nothing.

  • tlp.subject compares 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.resolve does 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, and psirt exits 2.

  • PyPI is published from a tag only, and after the suite. publish.yml compared tag
    and version for tags alone, so a dispatch from a branch published that branch; and it
    waited for no test. A test job, without the publishing token, now comes first.

  • The README examples say what the tool prints: "2 matching their signature" and
    the signature sentences of verify, which had changed since they were written.

  • .gitattributes keeps shell scripts LF. With core.autocrlf=true a Windows
    checkout turned release.sh into CRLF and bash stopped at set -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.yml can 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 a push: false
    build, before the login and before anything is pushed, so a rebuild of v2026.40 from
    a main holding 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 tagged main'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.yml was reachable by hand alone, so the only thing that built this
    image automatically was docker.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 after actions/checkout, which reaches into the step that
    extracts the version and names inputs.version for 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 analyze report. ARCHITECTURE.md section 7 separates facts from
    findings, and the console and Markdown reports showed only the facts: a
    signature_invalid of severity high reached the JSON and the count in batch and
    nobody reading analyze. Both now end with the findings, title and severity first.

  • "Provisions applied", as README and ARCHITECTURE.md section 5 describe.
    law_checker.check was 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).
    analyze now cites, in the console and in Markdown. The JSON is unchanged: it
    carries the findings, not the citations.

  • analyze --online, and offline by default. analyze cites from the local cache
    in ~/.exeradar and downloads nothing; --online downloads 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
    LICENSE out of the working tree on 2026-10-04 and the loss reached main: pyproject
    names the file, so python -m build failed with License 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
    through release.sh or scripts/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 than main,
    a dirty tree, a local main out 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.yml already 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.check takes offline instead of **context. The extra keywords were
    passed to findings_of and notes_of, which accept none, so any of them ended in a
    TypeError from 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 -Compress under
    $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 by test_catalog_encoding.py.
    Should it happen anyway, a ValueError from json.loads joins the OSError and
    SubprocessError path: "I could not tell", never a traceback out of analyze or
    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 --online reach 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", in tests/fixtures/first_teams_ey.json. Against main before the fixes,
    each converted test fails on the defect it protects.

Full Changelog: v2026.41...v2026.42