An OpenSSL advisory now reaches the copies other software carries
A CISA entry for OpenSSL, PHP, a Java runtime or libwebp now reaches the copies inside other software, found as files by the executables audit: on the first nine audited machines, 143 copies of OpenSSL on seven of them. Ubuntu and Debian packages are read against their own distribution's fixed build, and Firefox ESR is judged on its own release track.
A CISA advisory for OpenSSL now reaches the machines that carry a copy of it inside other software. On the first nine machines with an executables audit, that was 143 copies of OpenSSL on seven of them.
A library is rarely an installed program. OpenSSL ships inside Git, inside a VPN client, inside a backup agent, each with its own copy, and Windows PHP is a zip that registers nowhere.
Until 6 November an OpenSSL entry reached only the machines where OpenSSL was a package, and on Windows it rarely is one.
The card names the folder
Open Security briefing in the sidebar. A card for one of these flaws counts a machine once and gives each copy a line of its own, with the folder it sits in and the version written in the file. Your next step is that folder, or the software that put it there.
Four families are found as files: OpenSSL by its own Windows DLL names, PHP by its engine DLL, Java runtimes by java.exe, and libwebp.
OpenSSL and the PHP Group write each line's first fixed release in their CVE records, so a copy of those two is marked older or fixed on its line. Oracle names the affected Java releases instead of the fixed one, and no libwebp DLL we've seen carries a version, so those copies are listed for you to check.
This reads the executables audit, which Windows agents send once a day from 0.3.119. Linux and Mac machines send no file list, and their packages are read as before.
PHP is a software family now too, under the names your operators settled on for the PHP2Shell probe. CISA's two PHP2Shell entries, added on 26 October, were listed as naming software an agent can't see on every briefing until 6 November.
A Debian or Ubuntu package is read against its distribution's build
Canonical's 8.3.6-0ubuntu0.24.04.13 sorts below the PHP Group's 8.3.36 and carries the fix; Sury's 8.3.20 sorts above it and doesn't. So a PHP card said "installed on 6 machines" with every machine unjudged, while the threat probe for the same flaw said all six ran a fixed build. The two cards disagreed in tone about the same machines.
Since 10 November the briefing asks Ubuntu's CVE records and Debian's Security Tracker which build carries the fix, before any alert is decided, and reads each machine's package against the build named for its own release and its own source package. A card where every machine runs its distribution's fixed build moves to Already fixed, out of the to-do list and the alerts, the way a fixed browser card does.
Where a tracker names no build for a machine's release, the machine stays unchecked and the card says what it said before. Windows machines and RPM distributions aren't read this way.
A machine is read by every PHP package it carries, and the worst one decides. Until 12 November it was read by the first package the briefing's names found. A php7.4 left behind by a release upgrade stayed out of sight beside a fixed php8.3, and the card moved to Already fixed. A patched machine whose first PHP name was an extension built from another source, php8.3-apcu for one, went out as "check the versions". Now a second line no tracker names a build for keeps the machine unchecked, and the card names that package.
Firefox and Firefox ESR are two release tracks
They were one family, so comparing a version with Mozilla's per-track fixed releases meant nothing. Since 10 November firefox-esr, ESR-named Windows installs and Red Hat's bare firefox go to the ESR track, and a CISA Firefox entry reaches both tracks while the CVE record says which one a fix belongs to.
A row whose track can't be told, a bare firefox or a Mac install, is called older or fixed only when both tracks agree.
The same change gives a version verdict to Thunderbird, Notepad++, Plex,
SmarterMail, PaperCut and GitLab, each read on its own release line. The
makers who write no fixed release a comparison can use are listed in
documentation/briefing.md, each with its reason.
A file match is asked of the machine itself
A threat probe that matched a file waited for the next daily audit, so a file card could sit a day behind a machine that was just patched. The six-hourly pass now asks those machines through the agent's audit lookup, carrying nothing but the probe's own file names.
The agent answers from the list its last audit wrote, so the card reads "machine's own audit" with that list's time on it, and it doesn't say "live". Windows machines on 0.3.119 or newer, online at the time.
Also in this release
Password guessing on a domain controller is one finding. A bad Kerberos password logs event 4771 instead of 4625, so the guessing detector couldn't see it. 4771s now feed the same per-account count under the same label and threshold, with the failure codes and the services carried on the finding. A finding built from 4625s alone reads as it did before.
Your emails and report PDFs read German. Verification, invitation and password reset mails go out in the recipient's language; scheduled-report, uptime, critical-finding and honeytoken mails in the tenant's. All seven report PDFs put their covers, footers, section titles and verdicts through the same translations as the pages.
Lists sort, and remember how you left them. A table sorts from a click on its header or from the keyboard, with an arrow for the direction and blank cells last. The audit log is left out, being append-only and chronological.
MeshCentral device groups map to your clients. Link a group to a client on the Link devices page, and that client's Estate chapter lists the machines in the group that no Wegweiser agent reports, beside VSA's where both are mapped. MeshCentral stays read-only: the mapping and the shadow list read stored rows.