CVE-2020-15009
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAsusScreenXpertServicec.exe and ScreenXpertUpgradeServiceManager.exe in ScreenPad2_Upgrade_Tool.msi V1.0.3 for ASUS PCs with ScreenPad 1.0 (UX450FDX, UX550GDX and UX550GEX) could lead to unsigned code execution with no additional restrictions when a user puts an application at a particular path with a particular file name.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe AsusScreenXpertServicec.exe and ScreenXpertUpgradeServiceManager.exe in ASUS ScreenPad 2 Upgrade Tool V1.0.3 for ScreenPad 1.0 devices contain a binary planting vulnerability that allows unsigned code execution. The service executables load and run an application from a specific path with a specific filename without validation, enabling privilege escalation if an attacker places a malicious executable at that location.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if ASUS ScreenPad 2 Upgrade Tool is installedLook for the application in Add/Remove Programs (Windows) or check for the installation directory typically under C:\Program Files\ASUS\ScreenPad2 Upgrade Tool or similar locationsAffected if The application is present and version 1.0.3 is installed
-
Identify the vulnerable service executablesSearch for AsusScreenXpertServicec.exe and ScreenXpertUpgradeServiceManager.exe on the system - check installation directory and system service pathsAffected if Either executable is found on the system
-
Verify the installed versionRight-click each executable, select Properties, and check the File Version or Product Version fieldAffected if Version shows exactly 1.0.3 for either executable
-
Check if the vulnerable service is runningOpen Services console (services.msc) and look for ASUS ScreenXpert or ScreenPad Upgrade related services, or run 'sc query' to enumerate servicesAffected if A service associated with these executables is currently running
-
Identify the executable load pathUse process monitoring tools or examine the service configuration to determine the path from which the service loads executables without validationAffected if The service loads executables from a path that low-privilege users can modify
The system is affected if ASUS ScreenPad 2 Upgrade Tool version 1.0.3 is installed and the vulnerable service executables (AsusScreenXpertServicec.exe or ScreenXpertUpgradeServiceManager.exe) are present and running, with an exploitable path where unprivileged users can place malicious code.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable or remove the vulnerable ScreenPad 2 Upgrade Tool service, and restrict file system permissions on the path where the service searches for executables to prevent unauthorized code placement.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15009 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-15009 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data