How severe is GHSA-3c56-vx6v-q5vh?

GHSA-3c56-vx6v-q5vh has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-3c56-vx6v-q5vh?

GHSA-3c56-vx6v-q5vh affects the following packages: salt (PyPI), salt (PyPI), salt (PyPI), salt (PyPI), salt (PyPI), salt (PyPI), salt (PyPI), salt (PyPI), and 1 more. Ecosystems affected: PyPI.

How do I fix GHSA-3c56-vx6v-q5vh?

Update salt to 2015.8.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3c56-vx6v-q5vh is resolved across your whole dependency graph.

How do I detect GHSA-3c56-vx6v-q5vh in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for salt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3c56-vx6v-q5vh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-3c56-vx6v-q5vh actively exploited in the wild?

No public exploit code has been indexed for GHSA-3c56-vx6v-q5vh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3c56-vx6v-q5vh?

GHSA-3c56-vx6v-q5vh has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3c56-vx6v-q5vh?

GHSA-3c56-vx6v-q5vh is classified as CWE-732 (CWE-732). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3c56-vx6v-q5vh published, and has it been updated?

GHSA-3c56-vx6v-q5vh was published on May 24, 2022 and was last updated on October 22, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

SaltStack Salt Allows creating certificates with weak file permissionsGHSA-3c56-vx6v-q5vh

MEDIUM

GHSA-3c56-vx6v-q5vh is a medium-severity (CVSS 5.5) CWE-732 vulnerability in salt. A fix is available for salt — see the affected versions and patch details below.

Also known asCVE-2020-17490PYSEC-2020-105

Published

May 24, 2022

Updated

Oct 22, 2024

Affected

9 pkgs

Patched

9 / 9

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk-0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

9 pkgs affected

🐍salt🐍salt🐍salt🐍salt🐍salt🐍salt🐍salt🐍salt+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

The TLS module within SaltStack Salt through 3002 creates certificates with weak file permissions.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`salt`	all versions	2015.8.13`pip install --upgrade 'salt==2015.8.13'`
🐍PyPI	`salt`	≥ 2016.3.0&&< 2016.3.8	2016.3.8`pip install --upgrade 'salt==2016.3.8'`
🐍PyPI	`salt`	≥ 2016.11.0&&< 2016.11.10	2016.11.10`pip install --upgrade 'salt==2016.11.10'`
🐍PyPI	`salt`	≥ 2017.5.0&&< 2017.7.8	2017.7.8`pip install --upgrade 'salt==2017.7.8'`
🐍PyPI	`salt`	≥ 2018.2.0&&< 2018.3.5	2018.3.5`pip install --upgrade 'salt==2018.3.5'`
🐍PyPI	`salt`	≥ 2019.2.0&&< 2019.2.6	2019.2.6`pip install --upgrade 'salt==2019.2.6'`

Affected Products

2 products · 16 configurations

debian linuxdebian

2 versions

9.010.0

Application

saltsaltstack

≥ 3000.0 && < 3000.3

1 version

3001

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for salt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update salt to 2015.8.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3c56-vx6v-q5vh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

UbuntuMEDIUM

USN-6948-1Ubuntu

Frequently Asked Questions

The TLS module within SaltStack Salt through 3002 creates certificates with weak file permissions.

O3 Security · Impact-Aware SCA

Is GHSA-3c56-vx6v-q5vh in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works