DEV Community

kozhevniko
kozhevniko

Posted on

Greenbone on 3,657 hosts: the scanner that knows where every weakness is

Greenbone on 3,657 hosts: the scanner that knows where every weakness is

Greenbone, the company behind the OpenVAS scanner and the Greenbone Enterprise appliance family, publishes the vulnerability tests that many organisations rely on. A ZoomEye title query returns 3,657 matches for the product family, which is a small population with an unusual property: the systems in it are designed to hold a list of the weaknesses in everything they can reach.

Context and method

The measurement is one condition, title="Greenbone", run with sub_type=all and a page size of one. Page size limits how many records a response contains and does not affect the matched total reported for the condition.

A title match counts hosts that displayed the string when indexed. It does not distinguish a management console from an appliance login page, and it does not indicate whether the deployment is a production scanner or a test instance.

What the platform holds

A vulnerability scanner accumulates three kinds of valuable material.

The first is the asset inventory it has built. A scanner knows which hosts respond, which ports are open and which services announce their versions, because that is what it was configured to collect. An attacker who reads that inventory receives a target list that someone else assembled.

The second is the findings. Scan results record which systems have which unpatched software, and they are usually retained for reporting. A result set from last month is a ranked list of opportunities.

The third is the scanning credentials. To perform authenticated scanning, a scanner needs accounts on the systems it assesses, and authenticated scan results are more detailed than unauthenticated ones. An attacker who obtains those accounts inherits logon rights on a broad set of hosts.

The combination means a compromised scanner is both an intelligence source and a lateral movement path. That is a different risk profile from most of the platforms reviewed in this series.

Why exposure happens

Three patterns recur. A management interface configured to be reachable from a general administrative network because the security team works from several locations. A test deployment that was stood up to evaluate the product and never removed. And a hosted appliance whose default credentials or initial configuration were never changed, which is the failure mode the product's own documentation warns about.

Greenbone publishes advisories for its products, and the appliance families have a maintenance cycle that includes firmware updates. A deployment that has not been updated within that cycle should be treated as carrying its own known issues, in addition to the scan data it holds.

Reading 3,657 usefully

Because the population is small, the useful approach is direct verification rather than statistical argument. Identify the instances the organisation owns, confirm that the management interface is not reachable from outside the intended network, confirm that the credentials are intended for this deployment rather than the documented defaults, and review who holds accounts on the scanner.

Two additional items are specific to this class of tool. Confirm that the scan results are retained for the period the reporting requires and no longer, so that historical weakness data does not outlive its purpose. And confirm that the scanner cannot reach more of the network than the scope it was given, because a scanner with an open scope is an inventory of everything.

What ZoomEye contributes

A title query establishes the population and a country or hosting filter narrows it. For a tool of this class, the most useful application is defensive: run the query against your own address ranges to confirm that no scanner is visible from outside, and run it again after a review to demonstrate that the change held.

Limits

The figure is an indexed fingerprint and not a live scan. It provides no information about the configuration, the credentials or the scan data on any host, and nothing in this article suggests that any instance has been accessed without authorisation.

References

Top comments (0)