CVE is only detected when package is installed, not when it's built from source

Open
#128 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, shell, ubuntu
Domain
cli, devops, security

Research direction

Reproduce the two Dockerfile cases from the issue and compare the Scout CLI vulnerability results for the installed package and source-built PMIx image. Trace the CLI's image vulnerability detection entry point to determine whether the missing CVE is expected or a defect; done means the behavior is explained and, if defective, covered by a regression test.

Written by the indexing model from the issue text.

Description

Example CVE:

https://scout.docker.com/vulnerabilities/id/CVE-2023-41915?s=ubuntu&n=pmix&ns=ubuntu&t=deb&osn=ubuntu&osv=22.04&vr=%3E%3D0

Compare:

  1. Installing package
FROM ubuntu:22.04

RUN apt-get update && apt-get install -y libpmix2

CVE is detected.

  1. Building from source
FROM ubuntu:22.04

RUN apt-get update && apt-get install -y \
    wget \
    tar \
    libevent-dev \
    libhwloc-dev \
    build-essential \
    python3

ARG DOCKER_PMIX_VERSION=4.1.2
RUN wget https://github.com/openpmix/openpmix/releases/download/v${DOCKER_PMIX_VERSION}/pmix-${DOCKER_PMIX_VERSION}.tar.gz && \
    tar -xzvf pmix-${DOCKER_PMIX_VERSION}.tar.gz && \
    cd pmix-${DOCKER_PMIX_VERSION} && \
    ./configure --prefix=/usr/local && \
    make && \
    make install

RUN apt purge -y build-essential linux-libc-dev && apt autoremove -y

CVE is not detected

Is this expected?

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

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.

More from docker/scout-cli

All issues in docker/scout-cli

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.