# CVE-2020-17490: SaltStack Salt Allows creating certificates with weak file permissions > Weak file permissions on TLS certificates allow attackers to read sensitive keys, compromising secure communications in SaltStack deployments. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Nov 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-3c56-vx6v-q5vh, PYSEC-2020-105, UBUNTU-CVE-2020-17490 ## What is CVE-2020-17490? CVE-2020-17490 is a medium-severity vulnerability in Debian Debian Linux, published on 6 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description The TLS module within SaltStack Salt through 3002 creates certificates with weak file permissions. Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource) ## Which versions are affected by CVE-2020-17490? 19 open source packages ship an affected version, including salt. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `salt` | PyPI | All versions | 2015.8.10, 2015.8.13, 2016.3.4, 2016.3.6, 2016.3.8, 2016.11.3, 2016.11.6, 2016.11.10, 2017.7.4, 2017.7.8, 2018.3.5, 2019.2.5, 3000.3 | | `salt` | PyPI | All versions | 2015.8.13 | | `salt` | PyPI | All versions | 2015.8.13 | | `salt` | PyPI | From 2016.11.0 | 2016.11.10 | | `salt` | PyPI | From 2016.11.0 | 2016.11.10 | | `salt` | PyPI | From 2016.3.0 | 2016.3.8 | | `salt` | PyPI | From 2016.3.0 | 2016.3.8 | | `salt` | PyPI | From 2017.5.0 | 2017.7.8 | | `salt` | PyPI | From 2017.5.0 | 2017.7.8 | | `salt` | PyPI | From 2018.2.0 | 2018.3.5 | | `salt` | PyPI | From 2018.2.0 | 2018.3.5 | | `salt` | PyPI | From 2019.2.0 | 2019.2.6 | | `salt` | PyPI | From 2019.2.0 | 2019.2.6 | | `salt` | PyPI | From 3000 | 3000.4 | | `salt` | PyPI | From 3000 | 3000.4 | | `salt` | PyPI | From 3001 | 3001.2 | | `salt` | PyPI | From 3001 | 3001.2 | | `salt` | PyPI | From 3002 | 3002.1 | | `salt` | PyPI | From 3002 | 3002.1 | Products: Debian Debian Linux, Saltstack Salt. ## How do I fix CVE-2020-17490? Upgrade salt to a fixed version for your release line: 2015.8.10, 2015.8.13, 2016.3.4 or 2016.3.6. ## Is CVE-2020-17490 being exploited? There is no known exploitation of CVE-2020-17490 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-17490 and fix it if it is affected. What it is: CVE-2020-17490 is a medium-severity vulnerability in Debian Debian Linux, published on 6 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-17490 in the wild and no public exploit code. Affected packages and fixed versions: - salt (PyPI): affected all versions; fixed in 2015.8.10, 2015.8.13, 2016.3.4, 2016.3.6, 2016.3.8, 2016.11.3, 2016.11.6, 2016.11.10, 2017.7.4, 2017.7.8, 2018.3.5, 2019.2.5, 3000.3 - salt (PyPI): affected all versions; fixed in 2015.8.13 - salt (PyPI): affected all versions; fixed in 2015.8.13 - salt (PyPI): affected from 2016.11.0; fixed in 2016.11.10 - salt (PyPI): affected from 2016.11.0; fixed in 2016.11.10 - salt (PyPI): affected from 2016.3.0; fixed in 2016.3.8 - salt (PyPI): affected from 2016.3.0; fixed in 2016.3.8 - salt (PyPI): affected from 2017.5.0; fixed in 2017.7.8 - salt (PyPI): affected from 2017.5.0; fixed in 2017.7.8 - salt (PyPI): affected from 2018.2.0; fixed in 2018.3.5 - salt (PyPI): affected from 2018.2.0; fixed in 2018.3.5 - salt (PyPI): affected from 2019.2.0; fixed in 2019.2.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-17490/ (Markdown: https://insights.sbomify.com/CVE-2020-17490/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-17490 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-17490 - OSV: https://osv.dev/vulnerability/CVE-2020-17490 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-17490/ Summaries are generated and may contain mistakes; the official description above is the record.