CVE(1)

πŸ“¦
version 1.8.0 Β· 5 versions
, in fedora 44, ubuntu resolute, ubuntu stonking

πŸ’– CVE(1) β€” the cve manual, but make it make sense πŸ’–

okay bestie, sit down, hydrate, and let me tell you about cve β€” it's the CLI interface for the CVE Services API, and she is that girl. πŸŽ€


✨ NAME ✨

cve β€” a CLI interface for the CVE Services API. periodt. πŸ’…


✨ SYNOPSIS ✨

cve [OPTIONS] COMMAND [ARGS]...

like. that's the whole vibe. options, then a command, then whatever args that command wants. πŸ¦‹


✨ DESCRIPTION ✨

A CLI interface for the CVE Services API. that's it, that's the description. she's concise, she's iconic, she's not gonna waste your time. ✨


✨ OPTIONS ✨

okay so these are the global girlies β€” the flags that go before your command. read them carefully, some of them are literally required, no cap. πŸ‘‘

  • -u, --username TEXT β€” your username. you can also set it with the env var CVE_USER. this one is required, so don't skip her. πŸ’€
  • -o, --org TEXT β€” your CNA organization short name. env var: CVE_ORG. also required. yes bestie, you gotta say who you are. 🫢
  • -a, --api-key TEXT β€” your API key. env var: CVE_API_KEY. required too. all three of the big ones are mandatory, it's giving "no entry without the whole trio". πŸ”‘
  • -e, --env [prod|dev|test] β€” pick which deployment environment you wanna query. env var: CVE_ENVIRONMENT. your choices are literally just prod, dev, or test. choose wisely, prod is not a drill. 🌈
  • --api-url TEXT β€” throw in an arbitrary URL for the CVE API. env var: CVE_API_URL. for when you're feeling custom. ✨
  • -i, --interactive β€” makes it confirm create/update actions before actually executing them. env var: CVE_INTERACTIVE. lowkey the responsible bestie option, protect yourself. πŸ›‘οΈ
  • -V, --version β€” show the version and dip. bye! πŸ‘‹

✨ COMMANDS ✨

here's the whole roster, bestie. each one has her own dedicated manpage, and I'm linking you to every single one so you're never lost. πŸ’–

  • publish β€” Publish a CNA container of a CVE record... see cve-publish(1) for the full documentation on the publish command. πŸ“€
  • publish-adp β€” Add or update an ADP container in a CVE... see cve-publish-adp(1) for the full documentation on the publish-adp command. 🧚
  • reject β€” Reject a CVE record for a reserved or... see cve-reject(1) for the full documentation on the reject command. 🚫
  • undo-reject β€” Move a rejected CVE ID without a record... see cve-undo-reject(1) for the full documentation on the undo-reject command. ↩️
  • transfer β€” Transfer ownership of a CVE ID to another... see cve-transfer(1) for the full documentation on the transfer command. 🀝
  • reserve β€” Reserve one or more CVE IDs. see cve-reserve(1) for the full documentation on the reserve command. 🎟️
  • show β€” Display a specific CVE ID (and optionally... see cve-show(1) for the full documentation on the show command. πŸ‘€
  • list β€” Filter and list reserved CVE IDs owned by... see cve-list(1) for the full documentation on the list command. πŸ“‹
  • count β€” Display the total count of CVE records,... see cve-count(1) for the full documentation on the count command. πŸ”’
  • quota β€” Display the available CVE ID quota for... see cve-quota(1) for the full documentation on the quota command. πŸ“Š
  • user β€” Show information about a user. see cve-user(1) for the full documentation on the user command. πŸ™‹
  • org β€” Show information about your organization. see cve-org(1) for the full documentation on the org command. 🏒
  • validate β€” Validate a CVE record against the 5.1.1... see cve-validate(1) for the full documentation on the validate command. βœ…
  • ping β€” Ping the CVE Services API to see if it is up. see cve-ping(1) for the full documentation on the ping command. πŸ“
ngl bestie, if a command's description trails off with ... that's just how the original page do β€” the full tea lives in that command's own manpage. go read her. iykyk. πŸ’œ

okay that's the whole page!! this was version 1.8.0, dated 2025-09-29, from the cve manual. slay, go reserve some CVE IDs responsibly, and remember: three required flags, every time. mwah. πŸ’…βœ¨πŸŽ€πŸ¦‹πŸ’–

πŸ“¦ where this page comes from