pullcves(1)

πŸ’… pullcves β€” the cvechecker glow-up script

okay bestie, welcome to the pullcves Manual (that's pullcves(1) if you're being formal, which, like, we are not). This is the little script that keeps your local cvechecker CVE database and version matching rules fresh. It's giving maintenance era and honestly? Iconic. ✨


🌸 NAME

pullcves β€” update the local cvechecker CVE database and the version matching rules. That's the whole job. She does it well. πŸ’–


πŸ¦‹ SYNOPSIS

pullcves pull or
pullcves cleancache

(Yes, that's literally how the synopsis reads. Two vibes. Pick one. 🫢)


πŸŽ€ DESCRIPTION

so the pullcves script goes online, downloads the CVE entries from the Internet, and tucks them into your local cvechecker databases. Not only that β€” it also downloads the latest version matching rules from the Internet and loads those up into the cvechecker database too. Double duty, no complaints, slay.

For the actual downloading it uses the wget tool, and for the XML conversions it uses xsltproc. Those are the little helpers doing the heavy lifting behind the scenes. πŸ’…

Now, if you hit it with cleancache, it cleans its internal cache. Which means β€” and hear me out β€” it effectively removes the downloaded XML files (and the generated CSV files too), which causes the next pull to redownload and reimport everything. Full factory reset energy. Not a crisis, just a heads up that the next run is gonna be doing the most. 😭

Also, the pullcves script uses the configuration file of cvechecker to figure out the paths of the various locations, and it uses the same logic as everything else:

  • if CVECHECKER_CONFFILE is set as an environment variable, then it has to point to a valid configuration file
  • if that environment variable is not set, it tries ~/.cvechecker.rc, /usr/local/etc/cvechecker.conf and /etc/cvechecker.conf β€” in that order

fr fr, that's the whole lookup order, don't skip steps. 🌈


✨ USAGE

The command is simply:

pullcves pull or pullcves cleancache

That's it. That's the usage. Lowkey elegant. πŸ“

πŸ’€ RETURN CODES

The returncode of pullcves depends on the actions it performed. She's not mysterious, she's just specific.

In case of pull:

  • A returncode of 0 means that the CVE database and version matching rules were already up to date β€” nothing to do, we were already that girl πŸ‘‘
  • A returncode of 1 means that the CVE database is updated
  • A returncode of 2 means that the version matching rules are updated
  • A returncode of 3 means that both the CVE database and version matching rules are updated β€” double glow-up, we ate πŸ”₯
ngl if you get a 3 you should feel a little bit proud. That's both things refreshed in one go. Periodt.

🧚 AUTHOR

pullcves is part of the cvechecker tool. pullcves was written by Sven Vermeulen <sven.vermeulen@siphos.be>. Respect the author, bestie. πŸ’œ


August 17, 2013 β€” yeah, that's the date on this page, and 17 August 2013 is the same energy in a different outfit. That's the pullcves(1) manual, source and version included, signed off with a πŸŽ€ and a πŸ’–. Go pull some CVEs. iykyk. ✨

πŸ“¦ where this page comes from