Service interruption via migration requests
Published Apr 3, 2020 · Updated Sep 16, 2024
Uncontrolled resource consumption in affected rmt-server packages allows remote attackers to interrupt service via migration requests. SUSE identifies offline migration handling as the affected locus but does not disclose which resource is exhausted or which operation fails to bound it. No authentication or user interaction is required, and the documented consequence is limited to RMT service availability.
Summary
What happened
Uncontrolled resource consumption in affected rmt-server packages allows remote attackers to interrupt service via migration requests. SUSE identifies offline migration handling as the affected locus but does not disclose which resource is exhausted or which operation fails to bound it. No authentication or user interaction is required, and the documented consequence is limited to RMT service availability.
The record
- CVE
- CVE-2019-18904
- Published
- Apr 3, 2020
- Updated
- Sep 16, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Leap
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2020CVE 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=rmt-server <2.5.2-lp151.2.9.1
What conditions does exploitation require?
What is affected?
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