Unauthenticated system file deletion via missing authorization
Published May 26, 2021 · Updated Aug 5, 2024
Missing authorization in Red Hat redhat-certification 7 allows remote attackers to delete another host's system XML file. The /configuration view exposes the file-removal action without checking whether the requester owns the selected system file. No authentication is required, and the documented consequence is deletion of host-related XML data rather than arbitrary files.
Summary
What happened
Missing authorization in Red Hat redhat-certification 7 allows remote attackers to delete another host's system XML file. The /configuration view exposes the file-removal action without checking whether the requester owns the selected system file. No authentication is required, and the documented consequence is deletion of host-related XML data rather than arbitrary files.
The record
- CVE
- CVE-2018-10866
- Published
- May 26, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
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.
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