Command execution via one-time expired-token reuse
Published Feb 27, 2021 · Updated Aug 3, 2024
Insufficient session expiration in SaltStack Salt before 3002.5 allows remote attackers to execute commands with an expired eAuth token. The eAuth token-validation method returns usable token data for the first request after expiry instead of rejecting it with an empty result. Exploitation requires possession of a previously issued token and permits one post-expiration command against the Salt master or managed minions.
Summary
What happened
Insufficient session expiration in SaltStack Salt before 3002.5 allows remote attackers to execute commands with an expired eAuth token. The eAuth token-validation method returns usable token data for the first request after expiry instead of rejecting it with an empty result. Exploitation requires possession of a previously issued token and permits one post-expiration command against the Salt master or managed minions.
The record
- CVE
- CVE-2021-3144
- Published
- Feb 27, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-613, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo