docker / docker/scout-cli

Running docker scout on a built software reports a different version than it should

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

Nobody has claimed this yet.

Dominant language
Shell
Stars
454
Forks
134
PR merge metrics
No merged PRs in 30d

Description

I built ArgoCD from source:

mkdir argocd_build && \
    cd argocd_build && \
    mkdir gocache && \
    mkdir gopath && \
    export GOCACHE="$(realpath gocache)" && \
    export GOPATH="$(realpath gopath)" && \
    git clone https://github.com/argoproj/argo-cd  &&  \
    cd argo-cd && \
    git checkout master && \
    make clean && \
    make BIN_NAME=argocd-linux-amd64 GOOS=linux argocd-all

Built from 08cd54775046c6ca7071ebe4f5d817f2658cd3c9 (current master).

Docker Scout reports a CVE on it:

   1C     0H     0M     0L  github.com/argoproj/argo-cd/v3 3.0.0-20250826192237-08cd54775046
pkg:golang/github.com/argoproj/argo-cd@3.0.0-20250826192237-08cd54775046#v3

18: sha256:1326df62499f5e3478c1d5872b8acf7bbc3fad28394319df5c4a2327961e826f
/usr/local/bin/argocd (evident by)

    ✗ CRITICAL CVE-2025-47933 [Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')]
      https://scout.docker.com/v/CVE-2025-47933
      Affected range : <3.0.4                                        
      Fixed version  : 3.0.4                                         
      CVSS Score     : 9.0                                           
      CVSS Vector    : CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H  

Even though in the image it says:

$ /usr/local/bin/argocd version
argocd: v3.2.0+08cd547
  BuildDate: 2025-08-27T07:08:37Z
  GitCommit: 08cd54775046c6ca7071ebe4f5d817f2658cd3c9
  GitTreeState: clean
  GoVersion: go1.25.0
  Compiler: gc
  Platform: linux/amd64
{"level":"fatal","msg":"Argo CD server address unspecified","time":"2025-08-27T07:38:40Z"}

If I build from ArgoCD's newest tag (v3.1.1) then I cannot reproduce this issue.

Contributor guide

No contributing guide indexed for this repository

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

Reproduce the report using the provided ArgoCD source build and Docker Scout output, then compare Scout's detected Go module version with /usr/local/bin/argocd version. Trace how the CLI identifies the binary's version and maps CVEs. Done means the built commit is identified consistently and the reported vulnerability range matches the actual version.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go, shell
Domain
cli, devtools, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.