[Edge case] Missing key for fixed version

[ronniee007]

Description

Vulnerabilities do not reflect the key for fixed version in couple of cases, even though the fixed version is mentioned in description.

Example:
{
  "SchemaVersion" : 2,
  "Results" : [ {
    "Target" : "Java",
    "Type" : "jar",
    "Class" : "lang-pkgs",
    "Vulnerabilities" : [ {
      "VulnerabilityID" : "CVE-2022-4065",
      "LastModifiedDate" : "2023-04-29T07:15:00Z",
      "Description" : "A vulnerability was found in cbeust testng 7.5.0/7.6.0/7.6.1/7.7.0. It has been declared as critical. Affected by this vulnerability is the function testngXmlExistsInJar of the file testng-core/src/main/java/org/testng/JarFileUtils.java of the component XML File Parser. The manipulation leads to path traversal. The attack can be launched remotely. Upgrading to version 7.5.1 and 7.7.1 is able to address this issue. The name of the patch is 9150736cd2c123a6a3b60e6193630859f9f0422b. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-214027.",
      "Title" : "testng: a path traversal in zip files",
      "Severity" : "HIGH",
      "CVSS" : {
        "redhat" : {
          "V3Vector" : "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
          "V3Score" : 7
        },
        "nvd" : {
          "V3Vector" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
          "V3Score" : 7.8
        },
        "ghsa" : {
          "V3Vector" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
          "V3Score" : 7.8
        }
      },
      "Layer" : { },
      "PkgName" : "org.testng:testng",
      "DataSource" : {
        "ID" : "glad",
        "URL" : "https://gitlab.com/gitlab-org/advisories-community",
        "Name" : "GitLab Advisory Database Community"
      },
      "Ref" : "pkg:maven/org.testng/[email protected]?package-id=fe9fd45e9646795a",
      "InstalledVersion" : "7.0.0",
      "SeveritySource" : "nvd",
      "References" : [ "https://access.redhat.com/security/cve/CVE-2022-4065", "https://github.com/advisories/GHSA-rc2q-x9mf-w3vf", "https://github.com/cbeust/testng/commit/9150736cd2c123a6a3b60e6193630859f9f0422b", "https://github.com/cbeust/testng/pull/1596", "https://github.com/cbeust/testng/pull/2806", "https://github.com/cbeust/testng/releases/tag/7.7.0", "https://github.com/cbeust/testng/releases/tag/7.7.1", "https://github.com/testng-team/testng/pull/2899", "https://github.com/testng-team/testng/releases/tag/7.5.1", "https://groups.google.com/g/testng-users/c/V6jie-9uUIA", "https://nvd.nist.gov/vuln/detail/CVE-2022-4065", "https://vuldb.com/?ctiid.214027", "https://vuldb.com/?id.214027", "https://www.cve.org/CVERecord?id=CVE-2022-4065" ],
      "CweIDs" : [ "CWE-22" ],
      "DependencyType" : "Direct",
      "PrimaryURL" : "https://avd.aquasec.com/nvd/cve-2022-4065",
      "PublishedDate" : "2022-11-19T19:15:00Z"
    } ]
  }

Desired Behavior

Ideally the JSON output should have a fixed version key that can be extracted for further processing.

Actual Behavior

No key found. Description is a non-structured string, we can not rely on that field to extract the fixed version. Probably We need a machine learning to extract patterns from non-standard strings such as this.

Reproduction Steps

SBOM scanning and vulnerability reporting step for trivy binary

Target

Git Repository

Scanner

Vulnerability

Output Format

JSON

Mode

Standalone

Debug Output

None

Operating System

Google kubernetes

Version

v0.31.2

Checklist

• Run trivy image --reset
• Read the troubleshooting

[DmitriyLewen]

Hello @ronniee007
Thanks for your report!

We get fixed versions from databases.
In your case GitLab advisory database doesn't have fixed versions for CVE-2022-4065.

I created #235 to fix that.

[ronniee007]

Thank you @DmitriyLewen

[DmitriyLewen]

#235 has been merged.