ScanCode.io command injection in docker image fetch process

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.8 · CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H

EPSS

• CVE-2023-39523: 2.92% estimated exploitation activity in the next 30 days; percentile 87.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Command Injection in docker fetch process Summary A possible command injection in the docker fetch process as it allows to append malicious commands in the dockerreference parameter. Details In the function scanpipe/pipes/fetch.py:fetchdockerimage[1] the parameter dockerreference is user controllable. The dockerreference variable is then passed to the vulnerable function getdockerimageplatform. However, the getdockerimageplaform function constructs a shell command with the passed dockerreference. The pipes.runcommand then executes the shell command without any prior sanitization, making the function vulnerable to command injections. A malicious user who is able to create or add inputs to a project can inject commands. Although the command injections are blind and the user will not receive direct feedback without logs, it is still possible to cause damage to the server/container. The vulnerability appears for example if a malicious user adds a semicolon after the input of docker://;,…

Published by the source

9 Aug 2023, 14:41 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 13:12 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2ggp-cmvm-f62f

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2ggp-cmvm-f62f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-39523

Advisory: ScanCode.io command injection in docker image fetch process
IDs: CVE-2023-39523, GHSA-2ggp-cmvm-f62f
Record: https://patchnext.com/advisories/cve-2023-39523 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: scancodeio 32.5.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI scancodeio: affected <= 32.5.0; fixed in 32.5.1

## Suggested inspection (read-only)
- `python -m pip show scancodeio`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on scancodeio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2ggp-cmvm-f62f (OSV record GHSA-2ggp-cmvm-f62f lists affected ranges: PyPI scancodeio >=0 <32.5.1 (fixed))
- Verified: https://github.com/advisories/GHSA-2ggp-cmvm-f62f (GitHub-reviewed advisory GHSA-2ggp-cmvm-f62f lists affected ranges: PyPI scancodeio >=0 <=32.5.0)

Commands are suggestions: review each one before running it.