CVE-2021-3144
No exploitation reported by the sources we read.
- Published2021-02-27
- Fixed in3002.5 · 3002.3 · 3001.5 · 3001.4 · 3000.7 · 3000.6
- WeaknessCWE-613
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
Timeline
dates in UTC- 2021-02-2705:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2021-3144?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-3144?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3002.x | ≥ 3002, < 3002.5 | 3002.5 | NVD · OSV |
| 3002.x | ≥ 3002, < 3002.3 | 3002.3 | OSV |
| 3001.x | ≥ 3001, < 3001.5 | 3001.5 | OSV |
| 3001.x | ≥ 3001, < 3001.4 | 3001.4 | NVD · OSV |
| 3000.x | ≥ 3000, < 3000.7 | 3000.7 | OSV |
| 3000.x | ≥ 3000, < 3000.6 | 3000.6 | NVD · OSV |
| 2019.2 | ≥ 2019.2.6, < 2019.2.8 | 2019.2.8 | NVD · OSV |
| 2019.2 | ≥ 2019.2.0, < 2019.2.8 | 2019.2.8 | OSV |
| 2019.2 | ≥ 2019.2.0, < 2019.2.5 | 2019.2.5 | NVD · OSV |
| 2019.2 | ≥ 2018.3.0rc1, < 2019.2.0rc1 | 2019.2.0rc1 | OSV |
| 2017.x | ≥ 2017.5.0, < 2017.7.8 | 2017.7.8 | NVD · OSV |
| 2017.7 | ≥ 2017.7.0, < 2017.7.8 | 2017.7.8 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 9.0 | = 9.0 | no fix published | NVD |
| 10.0 | = 10.0 | no fix published | NVD |
| 11.0 | = 11.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 32.x | = 32 | no fix published | NVD |
| 33.x | = 33 | no fix published | NVD |
| 34.x | = 34 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Saltstack salt to 3002.5 · 3002.3 · 3001.5 · 3001.4 · 3000.7 · 3000.6 · 2019.2.8 · 2019.2.5
Advisories and patches
- saltproject.ioVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.19.1read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-613read 2026-10-23
- FIRST EPSSEPSS score5.1 %2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- Published
- 2021-02-27
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2021-3144?
Is CVE-2021-3144 actively exploited?
What is the CVSS score for CVE-2021-3144?
Running salt? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.