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

empty score with related vulnerabilities #734

Closed
HelenaSeidel opened this issue Apr 25, 2022 · 2 comments
Closed

empty score with related vulnerabilities #734

HelenaSeidel opened this issue Apr 25, 2022 · 2 comments
Labels
bug Something isn't working changelog-ignore Don't include this issue in the release changelog

Comments

@HelenaSeidel
Copy link

HelenaSeidel commented Apr 25, 2022

What happened:

vulnerabilities do not have a score if there is a related vul. (maybe only if the ids match)

alpine3.10.7_vulreport.zip
here an extract of the report:

{"matches": [
  {
   "vulnerability": {
    "id": "CVE-2021-28831",
    "dataSource": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28831",
    "namespace": "alpine:3.10",
    "severity": "High",
    "urls": [
     "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28831"
    ],
    "cvss": [],
    "fix": {
     "versions": [
      "1.30.1-r5"
     ],
     "state": "fixed"
    },
    "advisories": []
   },
   "relatedVulnerabilities": [
    {
     "id": "CVE-2021-28831",
     "dataSource": "https://nvd.nist.gov/vuln/detail/CVE-2021-28831",
     "namespace": "nvd",
     "severity": "High",
     "urls": [
      "https://git.busybox.net/busybox/commit/?id=f25d254dfd4243698c31a4f3153d4ac72aa9e9bd",
     ],
     "description": "decompress_gunzip.c in BusyBox through 1.32.1 mishandles the error bit on the huft_build result pointer, with a resultant invalid free or segmentation fault, via malformed gzip data.",
     "cvss": [
      {
       "version": "2.0",
       "vector": "AV:N/AC:L/Au:N/C:N/I:N/A:P",
       "metrics": {
        "baseScore": 5,
        "exploitabilityScore": 10,
        "impactScore": 2.9
       },
       "vendorMetadata": {}
      },
      {
       "version": "3.1",
       "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
       "metrics": {
        "baseScore": 7.5,
        "exploitabilityScore": 3.9,
        "impactScore": 3.6
       },
       "vendorMetadata": {}
      }
     ]
    }
   ],
   "matchDetails": [ ... ],
   "artifact": { ...  }
  }
]}

What you expected to happen:

the "root" vulnerability to have the proper score

How to reproduce it (as minimally and precisely as possible):

currently we see it when scanning alpine:3.10.7

Anything else we need to know?:

Environment:

  • Output of grype version: v0.35.0
  • OS (e.g: cat /etc/os-release or similar): reproduced on Z/OS :) and Ubuntu 20.04/amd64
@joshbressers
Copy link
Contributor

I don't think this is a bug. If you look at "vulnerability" and "relatedVulnerabilities" they are two different data sources.

The "vulnerability" data comes from Alpine. Alpine does not include CVSS scores but they do include severity for example.

The "relatedVulnerabilities" is coming from NVD and includes the CVSS score because NVD includes this data.

@tgerla
Copy link
Contributor

tgerla commented Aug 4, 2022

Hi @seidkevi, we are going to go ahead and close this issue. Please let us know if you need anything else. Thanks!

@tgerla tgerla closed this as not planned Won't fix, can't repro, duplicate, stale Aug 4, 2022
@tgerla tgerla moved this to Done in OSS Aug 4, 2022
@wagoodman wagoodman added the changelog-ignore Don't include this issue in the release changelog label Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working changelog-ignore Don't include this issue in the release changelog
Projects
Archived in project
Development

No branches or pull requests

4 participants