Vuls collects vulnerability information from hosts and stores reports that can be viewed through a terminal interface or the accessory VulsRepo web UI. A small web footprint does not make the reports unimportant. The dashboard can reveal host names, operating systems, installed packages, and known vulnerabilities.

Observation

At 07:51 on November 20, 2026 (UTC+8), a count-only ZoomEye SDK query used sub_type=all, page 1, and pagesize 1. app="VulsRepo" returned 0 matches. title="VulsRepo" returned 6 matches.

Six title matches are a manageable review set. They may still include documentation, test deployments, and pages that merely mention the project. The zero application count means ZoomEye did not confirm a product fingerprint for this exact query.

The report is the sensitive asset

Vuls documentation lists scan results and relationships between scanned hosts as part of its core function. VulsRepo presents those results in a web interface. Reviewing the HTTP login page is not enough if report data, static assets, or an unauthenticated reverse-proxy path can be reached directly.

For each deployment, identify where Vuls stores its database and log directory, how VulsRepo reads them, and whether the dashboard has authentication at the application or proxy layer. Check the http configuration described by the Vuls documentation and confirm whether all routes inherit the same protection.

A useful test is to request the dashboard root, a known report path, and static assets without a session. Then repeat with a low-privilege account if the deployment supports one. Compare the behavior with the proxy configuration instead of assuming that an HTML login screen covers every route.

Protect the target map

The scan configuration itself can expose SSH targets, jump hosts, credentials by reference, and scan schedules. Treat the Vuls configuration and database as sensitive even if the web UI is internal. Backups should be encrypted and access logs should be retained separately from the scanned hosts.

Review whether VulsRepo can write or trigger scans or whether it is read-only. The answer changes the impact of an exposed session. Confirm the application's trusted proxy headers and do not let client-supplied identity headers bypass the proxy login.

The six title matches are a precise starting point for a small inventory. ZoomEye has shown a candidate population, while the control decision depends on report storage, proxy coverage, and the identity allowed to view vulnerability data.

References