Skip to content
Fencer Vulns
medium 4.2

CVE-2023-20898 json

Salt can cause Git Providers to get wrong data

published 2023-09-05 3 y ago modified 2026-06-17 4 mo ago also GHSA-qvh6-3j7x-3hq7 , PYSEC-2023-169 , EUVD-2023-0231

cvss
4.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

Git Providers can read from the wrong environment because they get the same cache directory base name in Salt masters prior to 3005.2 or 3006.2. Anything that uses Git Providers with different environments can get garbage data or the wrong data, which can lead to wrongful data disclosure, wrongful executions, data corruption and/or crash.

Patch / fix

  • pypi salt 3005.2, 3006.2
  • saltstack salt 3005.2, 3006.2
  • release-notes-susemanager Manager Server 4.3 4.3.8-150400.3.77.1
  • release-notes-susemanager-proxy Manager Proxy 4.3 4.3.8-150400.3.61.2
  • venv-salt-minion Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS, EL-9:Update:Products:SaltBundle:Update 3006.0-1.24.1
  • saltbundlepy EL-9:Update:Products:SaltBundle:Update 3.10.10-1.9.1
  • saltbundle-zeromq EL-9:Update:Products:SaltBundle:Update 4.2.3-1.6.2
  • saltbundlepy-cffi EL-9:Update:Products:SaltBundle:Update 1.15.1-1.6.1
  • saltbundlepy-core EL-9:Update:Products:SaltBundle:Update 3.10.10-1.9.1
  • saltbundlepy-kiwi EL-9:Update:Products:SaltBundle:Update 9.24.43-1.9.1

suse advisories SUSE-SU-2023:3885-1SUSE-EL-9-CLIENT-TOOLS-2023-3884SUSE-SU-2023:3884-1SUSE-SU-2023:3877-1SUSE-SU-2023:3876-1SUSE-SU-2023:3866-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-20898 updated cvss 4.2

salt: Git Providers can read from the wrong environment

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.2 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 4.2 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
OSV 3.1 7.8 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi salt
<3005.2
>=3006.0rc1, <3006.2
>=3006.0, <3006.2
3005.2
3006.2

Affected products

  • n/a Salt

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.