Unauthenticated privilege escalation via insufficient control flow
Published Apr 15, 2020 · Updated Aug 4, 2024
Insufficient control flow in Intel Compute Module MFS2600KI all versions allows remote attackers on an adjacent network to escalate privileges. Intel has not published the affected firmware component, control-flow path, or the operation that untrusted adjacent input can improperly direct. No authentication is required, and successful exploitation changes integrity across a security boundary without reported data disclosure or service interruption.
Summary
What happened
Insufficient control flow in Intel Compute Module MFS2600KI all versions allows remote attackers on an adjacent network to escalate privileges. Intel has not published the affected firmware component, control-flow path, or the operation that untrusted adjacent input can improperly direct. No authentication is required, and successful exploitation changes integrity across a security boundary without reported data disclosure or service interruption.
The record
- CVE
- CVE-2020-0577
- Published
- Apr 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Intel
- Product
- Intel Compute Module MFS2600KI
- Classifications
- T1068
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=See provided reference
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