Repository navigation
Releases
cvescope 0.2.3
Less noise, and a warning when the schedule stops.
Know when syncs stop
Every full cvescope sync now records when it finished and which feeds or collectors failed. The page header shows "synced N ago". A banner appears in three cases:
- The last full sync is older than
serve.stale_after_hours(default 12). - No full sync has ever been recorded.
- A feed or collector failed in the last run. The banner names which one.
cvescope status reports the same. A scheduled sync that quietly stopped no longer goes unnoticed.
Less noise
- Auto-updating apps. For Chrome, Edge, Firefox, Thunderbird, VS Code, Signal, Telegram and Bitwarden, a CVE record with no version data that's more than a year old counts as not affected.
- Distro and vendor builds. A "check" on a backported build (a Proxmox kernel, the FreeBSD base, a package no tracker answered) only surfaces once it's actually exploited ("act now"). A PoC or high EPSS alone no longer puts it in "watch".
Fix: removed packages
dpkg-query -W also lists packages that were removed but left config files behind (rc). The dpkg collector counted them as installed, which could show Apache on a box that no longer runs it, or an old OpenSSL left over from a release upgrade. Add the status column to your dpkg command:
dpkg-query -W -f='${db:Status-Abbrev} ${Package} ${Version} ${source:Package}\n'
Only installed packages (ii, hi) count now. Lists without the column still parse, but can't tell the difference. osquery's deb_packages gets the same filter through its status column.
Upgrading
pip install --upgrade git+https://github.com/magikh0e/cvescope@v0.2.3
Update any dpkg collector command as shown above. The wiki has the full example.
cvescope 0.2.2
A small release for running cvescope unattended.
New: --log FILE
A global option that appends everything a run prints to a file, rotated at 5 MB. If a run crashes, the traceback goes into the log too instead of disappearing. Use it for cron and Task Scheduler runs, where nobody is watching the console:
cvescope --log ~/.local/share/cvescope/sync.log sync
Scheduling docs
The README and the wiki now show a full Windows Task Scheduler setup in PowerShell:
pythonw, so no console window pops up.- Catch-up after sleep.
- No overlapping runs.
- The task runs as you, so it sees your config and environment variables.
Project
- Issue forms for wrong or missing matches, bugs, collector requests and ideas. Questions go to Discussions.
- A wiki covering installation, configuration, every collector, matching, tiers and alerts, data sources, troubleshooting and contributing.
Upgrading
pip install --upgrade git+https://github.com/magikh0e/cvescope@v0.2.2
cvescope 0.2.1
osquery, live. The osquery collector can now run osqueryi itself instead of reading saved files. With osquery installed, a plain block is enough:
[[inventory]]
type = "osquery" # this machine
[[inventory]]
type = "osquery"
name = "nas"
command_prefix = ["ssh", "nas"] # another host over sshIt picks queries for the OS it finds:
- Windows: installed programs plus the exact build, update revision and release, so Microsoft's version ranges match precisely.
- macOS: apps and Homebrew packages.
- Linux: Debian/Ubuntu or RPM packages plus the kernel. Debian and Ubuntu packages go through the distro trackers added in 0.2.0.
queries = [...] replaces the defaults, and osqueryi = "..." points at a non-standard install. With a path, it reads saved results exactly as before. osquery only reads the host's own state, so cvescope still never scans anything.
Fixes
- Microsoft Edge no longer matches CVEs for the pre-2021 EdgeHTML browser, which shared the plain "Microsoft Edge" name in old records.
Also
- The README and package metadata link the write-up at https://magikh0e.pl/pubCode/cvescope.html.
Upgrading
pip install --upgrade git+https://github.com/magikh0e/cvescope@v0.2.1
cvescope 0.2.0
cvescope can now see much more of what you run, and distro packages get real answers instead of "check".
New: Debian and Ubuntu security trackers
Distros backport fixes, so an upstream version inside an affected range often isn't vulnerable. cvescope now asks the distro. Debian data comes from the Debian security tracker (via OSV), Ubuntu data from Canonical's per-release OVAL. Only the releases your hosts run are downloaded: Debian is ~80 MB, refetched only when it changes, and Ubuntu is ~2 MB per release. Packages from dpkg, from osquery deb_packages, and from Debian/Ubuntu VMs get the tracker's fixed/affected verdict. Debian issues rated "unimportant" count as not affected.
New inventory sources
proxmoxnow lists every VM and container. VMs with the QEMU guest agent report their OS and kernel (guests = falseto turn it off).docker: the app in each running Docker/Podman container, from its image tag or version label, locally or over ssh.osquery: osqueryi JSON, osqueryd result logs, or the JSON from the newexamples/windows-inventory.ps1, which records the exact Windows build (so Microsoft's CVE ranges match precisely) plus installed programs. About 50 common programs are mapped by name.nmap_xml: every open service annmap -sVscan identified. cvescope still never scans; you run nmap.wpscanandwhatweb: WordPress core, theme and plugin versions, and web stack versions, from those scanners' reports.
Also
dpkgreads os-release and source package names;packages = "all"covers every source package.- CVE records'
packageNameis indexed, which is how WordPress plugin advisories name the plugin. cvescope synccollects the inventory before fetching feeds, so the distro source knows which releases to get.- A logo: README badge, social preview card, and an SVG favicon for the page.
Upgrading from 0.1.0
pip install --upgrade git+https://github.com/magikh0e/cvescope@v0.2.0
cvescope sync --rebaseline # optional: re-import once so packageName gets indexed for existing CVEs
Without --rebaseline, package names are picked up as CVE records update. The Proxmox collector now adds your VMs and containers by default, so expect new inventory items and matches on the first sync.
cvescope 0.1.0
First release.
cvescope asks your gear for its versions, matches them against the full CVE List, and ranks what's left by real-world exploitation evidence: CISA KEV, CISA SSVC, Metasploit, Nuclei, Exploit-DB, public PoCs and EPSS. It then alerts you when that evidence changes for something you run.
What's in it
- CVE List (cvelistV5) baseline plus delta updates, including CISA Vulnrichment
- Exploitation signals: KEV, EPSS, Metasploit, Nuclei, Exploit-DB, PoC-in-GitHub (metadata only, never cloned), your own exploit folders
- Collectors: Proxmox VE, OPNsense, UniFi Network, Pi-hole v6, Home Assistant, plus static, command, dpkg and http_json for anything else
- Certificate pinning for self-signed appliances, checked before any credential is sent
- Act now / watch / info tiers, change tracking, alerts via ntfy, Home Assistant or a webhook
- Local web page and a CLI
- Python 3.11+, standard library only
Getting started
pip install git+https://github.com/magikh0e/cvescope
cvescope init
cvescope sync
cvescope serve
The first sync downloads about 750 MB. Try examples/demo.toml to see it on a made-up network first.