DataMiner's 1,482 Title Matches Do Not Find BrokerGateway
DataMiner's 1,482 Title Matches Do Not Find BrokerGateway
Tag archive
DataMiner's 1,482 Title Matches Do Not Find BrokerGateway
Signal K: 558 Title Matches, 1,085 Body Matches, and a Path Traversal With a Visibility Condition
A mail daemon that cannot serve HTTP returns 30.7 million application matches and 32 titles, and the listener layer is where the usable numbers are.
Six products measured repeatedly over five weeks move by less than one percent a month, one of them fell, and the drift floor tells you what a real change looks like.
A zero title count beside 622 body matches, and why administration consoles rarely carry the product family name in their tab.
Why a Struts body count near a million says nothing about vulnerable applications, and what a bill of materials answers instead.
Argo CD has the largest public footprint measured in this series at 62,236 fingerprinted hosts, yet only 0.8% still answer on the port its documentation uses.
1,689,755 hosts answer on the rsync daemon port. The module list is readable before authentication, and the write behaviour depends on three configuration options.
2.1 million services answer on port 8009, and 620,164 of them reply to an HTTP request. The AJP connector is the port inventories forget.
Four AD FS measurements, why certificate common names overcount the population, and which endpoint should be the only published one.
How to read 4,802, 985 and 0 from the same advisory set, and why a zero match is a visibility limit rather than a deployment finding.
A CVE dork returning zero is a statement about the index, not about exposure. What 62,245 Argo CD fingerprints, 25,097 on port 443 and an empty CVE match actually tell you.