Server crash via cyclic service imports
Published Mar 7, 2021 · Updated Sep 16, 2024
Denial of service in NATS.io NATS Server 2.0.0 through 2.1.9 allows remote authenticated users to crash the server via cyclic service imports. The AddServiceImportWithClaim path accepted an import without checking overlapping exports and reverse imports, so a cycle repeatedly consumed CPU and memory. Exploitation requires control of at least two accounts on a service exposed to untrusted account holders and kills the server after resource exhaustion.
Summary
What happened
Denial of service in NATS.io NATS Server 2.0.0 through 2.1.9 allows remote authenticated users to crash the server via cyclic service imports. The AddServiceImportWithClaim path accepted an import without checking overlapping exports and reverse imports, so a cycle repeatedly consumed CPU and memory. Exploitation requires control of at least two accounts on a service exposed to untrusted account holders and kills the server after resource exhaustion.
The record
- CVE
- CVE-2020-28466
- Published
- Mar 7, 2021
- Updated
- Sep 16, 2024
- Vendor
- NATS.io
- Product
- NATS Server
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 7, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <unspecified
What conditions does exploitation require?
What is affected?
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