Unauthenticated service interruption via EDS decompression
Published Jun 15, 2020 · Updated Aug 4, 2024
Resource-exhaustion DoS in Rockwell Automation FactoryTalk Linx 6.00, 6.10, and 6.11 allows remote attackers to interrupt service. Its EDS-upload communication function accepts a rogue EDS.gz file whose bad compression drives decompression until all CPU resources are consumed. No authentication or user interaction is required, and successful exploitation exhausts processor capacity rather than exposing or modifying data.
Summary
What happened
Resource-exhaustion DoS in Rockwell Automation FactoryTalk Linx 6.00, 6.10, and 6.11 allows remote attackers to interrupt service. Its EDS-upload communication function accepts a rogue EDS.gz file whose bad compression drives decompression until all CPU resources are consumed. No authentication or user interaction is required, and successful exploitation exhausts processor capacity rather than exposing or modifying data.
The record
- CVE
- CVE-2020-12005
- Published
- Jun 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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