Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Research: VEX consumption #9606

Open
rjmateus opened this issue Jan 9, 2025 · 0 comments
Open

Research: VEX consumption #9606

rjmateus opened this issue Jan 9, 2025 · 0 comments

Comments

@rjmateus
Copy link
Member

rjmateus commented Jan 9, 2025

Description

Uyuni has a feature that performs a CVE analysis on the managed machines. That analysis is done by comparing the installed package version with metadata of those packages and which CVE identifiers are associated with it.

Currently, this metadata is obtained using two independent methods:

  1. Package released metadata
  2. OVAL data files (see https://oval.mitre.org/)

The scanner process is also split and it can independently perform the analysis based on package metadata or OVAL metadata.

Linux OS companies are planning on replacing OVAL with VEX definition. In 2023 Red Hat announced support for VEX and was planning to replace OVAL with VEX by the end of 2024. SUSE also publishes VEX data so it could be good for a student to look into it.

Tasks overview

  • Download, process, and save to the database the metadata information in the VEX format.
  • Enhance the scanner process to consider this new method.

As part of this research, we should also consider if it's possible to use the same database tables as for OVAL data, and re-use also the same scan process/method.

Languages and technologies

  • VEX processor: Python
  • Scanner: Java

Next steps

  • ?

Mentors

@admd ?
@parlt91 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant