CVE-2020-7817
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 · uneditedMyBrowserPlus downloads the files needed to run the program through the setup file (Setup.inf). At this time, there is a vulnerability in downloading arbitrary files due to insufficient integrity verification of the files.
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 confidenceMyBrowserPlus downloads program files through a Setup.inf file without properly verifying the integrity of those files. This allows an attacker to inject or replace downloaded files with arbitrary malicious content, potentially leading to code execution on victim machines.
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<= 6.2.2018.529CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Verify Raonwiz K Upload installationCheck for the presence of Raonwiz K Upload in the system by looking for its installation directory (commonly in Program Files) or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Raonwiz K Upload' or similar.Affected if The software is installed on the system
-
Determine installed versionLocate the executable (typically named KUpload.exe or similar) and right-click to view Properties, or use command: dir "C:\Program Files\Raonwiz" /s /b 2>nul to find the program files, then check version info.Affected if The version number is 6.2.2018.529 or lower
-
Identify Setup.inf download mechanismSearch for Setup.inf files within the application directory and any user-accessible download/update folders. Use: dir /s C:\Setup.inf or search the application installation folder.Affected if Setup.inf files exist and are used by the application for downloading additional components
-
Check for unverified download behaviorReview the application's update mechanism or logs to see if files are downloaded without integrity verification. Monitor network traffic or inspect configuration files in the application directory for download URLs.Affected if The application downloads files from remote sources without SHA-256 hash or signature verification
If Raonwiz K Upload version 6.2.2018.529 or lower is installed and uses Setup.inf for downloading program files without integrity verification, the environment is affected by CVE-2020-7817.
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 dataImplement cryptographic integrity verification (e.g., SHA-256 hashes or digital signatures) for all downloaded files and verify them before execution. Use secure channels with TLS and add tamper-evident mechanisms to the update/download process.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7817 — 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-7817 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