Unauthenticated code execution via unverified upgrade file
Published Mar 3, 2020 · Updated Aug 4, 2024
Code execution in Naver Cloud Explorer 2.2.2.11 and earlier allows remote attackers to run a downloaded file during an upgrade. The upgrade mechanism accepts a file from an attacker-controlled server, downloads it without verifying its integrity, and executes it. No authentication or user interaction is required; successful exploitation runs attacker-supplied code in the updater's context, although NAVER has not identified the responsible function or update protocol.
Summary
What happened
Code execution in Naver Cloud Explorer 2.2.2.11 and earlier allows remote attackers to run a downloaded file during an upgrade. The upgrade mechanism accepts a file from an attacker-controlled server, downloads it without verifying its integrity, and executes it. No authentication or user interaction is required; successful exploitation runs attacker-supplied code in the updater's context, although NAVER has not identified the responsible function or update protocol.
The record
- CVE
- CVE-2020-9751
- Published
- Mar 3, 2020
- Updated
- Aug 4, 2024
- Vendor
- NAVER Corporation
- Product
- Naver Cloud Explorer
- Classifications
- CWE-494, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 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=unspecified <=2.2.2.11
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