jfrog / jfrog/jfrog-cli-security

Include Fixed Version Field in Xray Scan Build Output

Open
#444 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
13
Forks
50
Avg merge
3d 48m
Merged PRs (30d)
26

Description

In the xray scan build response the fixed version information is not garunteed to be present. If the vulnerability description does not include the last version affected or the first fixed version, then the user must open the Xray web application to review the vulnerability.

The goal is to have all relevant scan information included in the build log output.

Example:

{
      "severity" : "Medium",
      "type" : "security",
      "provider" : "JFrog",
      "created" : "2019-03-03T00:07:09.904-08:00",
      "summary" : "It was found that the GnuTLS implementation of HMAC-SHA-256 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data using crafted packets.",
      "description" : "It was found that the GnuTLS implementation of HMAC-SHA-256 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data using crafted packets.",
      "cve" : "CVE-2018-10844",
      "impacted_artifacts" : [ {
        "name" : "...",
        "path" : "art1/builds/",
        "sha256" : "f10ff78a72b54e1feb1610cad046d5c6a2e6c8322c1392f7b5a942960c2ea25e",
        "sha1" : "8d10ef8436e387a330e195a0cbc6ad9c6a19138a",
        "depth" : 0,
        "pkg_type" : "Build",
        "parent_sha" : "f10ff78a72b54e1feb1610cad046d5c6a2e6c8322c1392f7b5a942960c2ea25e",
        "display_name" : "...",
        "infected_files" : [ {
          "name" : "gnutls28:3.5.18-1ubuntu1",
          "path" : "",
          "sha256" : "0f6e016976ac18f20d606293997d8c9e1f248726a5642acfb2bb959989b02169",
          "depth" : 0,
          "pkg_type" : "Debian",
          "parent_sha" : "898c46f3b1a1f39827ed135f020c32e2038c87ae0690a8fe73d94e5df9e6a2d6",
          "display_name" : "ubuntu:bionic:gnutls28:3.5.18-1ubuntu1"
        }]
       }]
     }

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Xray scan build response that produces the build log output; the issue names no files or tests. Confirm the output includes fixed-version information when available and remains complete when the vulnerability description omits version data.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.