Both PaperCut CVE records published the fix as "24.1.10, 25.0.13, 26.0.5" in one field typed as semver.
NVD resolved that into ranges ending at 24.1.9, 25.0.12, 26.0.4.
One release short. A tool that takes those ranges as written calls a vulnerable server fixed.
1
63
Joe Silva on the two events that should reopen a mitigated finding, and the one question to ask about each control:
lnkd.in/p/dmFWX4bh
1
N-able shipped an N-central hotfix two days after Sean Bales published 33 flaws, then a second six days later. Both tell customers to upgrade their Agents and Probes.
That instruction assumes you know you are a customer. The Agent a former MSP left behind did not get the memo.
1
7
Across Spektion deployments, 50 to 80% of critical CVEs turn out not to require action.
Severity is the one column every patch queue already has. In November it ranked the exploited CVE behind 63 others.
lnkd.in/p/g4KJUgW6
13
A 30-minute VM self-test: count what your top vendor fixed in its last three releases against what your scanner flagged.
Joe Silva adds a third column: how that software behaves on your hosts.
A scan-first program fills it with a version string.
lnkd.in/p/enrvgnys
5
TrueConf patched an unauthenticated server bug in June. Kaspersky says attackers were exploiting it by July. The CVE came in August.
For a scan-first program, that bug did not exist for about two months, including the month someone was exploiting it.
spektion.com/articles/disclo…
53
Find the configs pointing at archived reference servers. Switch to the service owner's own server, and approve one MCP server per service.
Six slides:
linkedin.com/feed/update/urn…
6
Spektion identifies undisclosed vulnerabilities before a CVE is published and ships a control when there is no patch.
David Westcott's post:
linkedin.com/posts/westcottd…
21





