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

False Positives in SUSE 12 SP3 Teradata kernels #2024

Closed
wagde-orca opened this issue Sep 11, 2024 · 0 comments · Fixed by #2025
Closed

False Positives in SUSE 12 SP3 Teradata kernels #2024

wagde-orca opened this issue Sep 11, 2024 · 0 comments · Fixed by #2025
Assignees
Labels

Comments

@wagde-orca
Copy link
Contributor

wagde-orca commented Sep 11, 2024

What did you do? (required. The issue will be closed when not provided.)

I scanned SUSE 12 SP3 with Teradata kernel installed (4.4.140-96.126.TDC.1) and we get hundreds of CVEs that is resolved in this version like CVE-2016-10905, vuls says that the fix version is 0:4.4.180-94.156.1 (not TDC) although the real fixed version is 4.4.140-96.97.TDC.1 as it appears in the oval file https://ftp.suse.com/pub/projects/security/oval/suse.linux.enterprise.server.12.xml.gz

I verified that the CVE and proper fixed version are in the oval DB
kernel-default,0:4.4.121-92.169.1,5
kernel-default,0:4.4.180-94.156.1,6
kernel-default,0:4.4.140-96.97.TDC.1,6
so the bug is in vuls and how we query the suse oval DB for the kernel-default package.

What did you expect to happen?

i expected not to see this CVE and many other CVEs

What happened instead?

We got 100s of old/fixed/FP cves that are fixed inthe installed kernel-default

I think that for teradata packages (which are mainly kernel related packages) we should check the TDC entries in the DB and not the "regular" ones

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

Successfully merging a pull request may close this issue.

2 participants