cve-check-tool icon indicating copy to clipboard operation
cve-check-tool copied to clipboard

Original Automated CVE Checking Tool

Results 30 cve-check-tool issues
Sort by recently updated
recently updated
newest added

Consider using an alternative and faster backend later in the cycle

After upgrading to version 5.6.4 from the previous one, when a tool tries to update the database, this happens: process_node(): attempt to write to a readonly database process_node(): attempt to...

The template lib is currently fairly primitive, working on an interpret-in-place concept, meaning that advanced child contexts and per-list-context is somewhat shaky. For better integration into "status" pages and report...

The current JIRA plugin needs reworking to better fit an actual plugin API, i.e. to be disconnected from the internals and loaded at runtime. `PLUGIN_TYPE_BTS` might even work here. Also...

help wanted
approved

Connect plugin using new API interface

De-glib the code to align with the main program.

As we expand we'll need to support formats other than just `src.rpm` archives, such as debian source packages. As such we should add a successor option, and retain compatibility.

approved

For example following line in faux crashes cve-check-tool: linux_kernel,3.10.17,,, ## Starting program: /usr/bin/cve-check-tool -t faux pkgs.txt [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV,...

PKGBUILD may offer simplicity, but in terms of being machine readable it's an absolute nightmare, and to fully parse it correctly requires execution of sub shells, thus the format in...

approved

The NVD is but a data source, albeit the primary validation for a CVE ID. As such it should be relegated to this status, and make use of the `CvePlugin`...

approved