CVE-2020-7808
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 · uneditedIn RAONWIZ K Upload v2018.0.2.51 and prior, automatic update processing without integrity check on update module(web.js) allows an attacker to modify arguments which causes downloading a random DLL and injection on it.
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 RAONWIZ K Upload software (versions up to v2018.0.2.51) has a critical vulnerability in its automatic update mechanism. The update module (web.js) lacks integrity verification, allowing attackers to manipulate update arguments and cause the application to download and execute a malicious DLL via DLL injection, achieving remote code execution.
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<= 2018.0.2.51CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify the installed version of Raonwiz Raon K UploadLocate the software installation directory and check version information (typically in application properties, about dialog, or version file). Compare the found version to the affected range: versions up to and including 2018.0.2.51Affected if The installed version is 2018.0.2.51 or earlier
-
Determine if automatic update is enabledCheck the application's settings, configuration files, or preferences for an 'automatic update' or 'auto-update' feature. Look for update-related configuration in the software's data directory or registry keys if applicableAffected if Automatic update functionality is turned on or configured to check for updates automatically
-
Locate and inspect the update module (web.js)Find the web.js file within the application's installation directory, typically in a folder related to updates or the main application modules. Open the file and search for functions related to update downloading, DLL loading, or integrity verificationAffected if The web.js file exists and lacks code for signature verification, HMAC validation, or other integrity checks before downloading or executing updates
-
Examine update configuration for verification settingsLook for configuration files that govern the update process (such as config.json, update.config, or similar). Check if these files contain settings for code signing, checksum validation, or trusted update server definitionsAffected if No integrity verification settings are defined or configured for the update mechanism
-
Review DLL loading behavior during updatesIf possible, monitor or inspect how the application loads DLLs during the update process. Check if the application loads DLLs from the update without validating their origin or signatureAffected if The application loads and executes DLLs from the update process without signature or integrity validation
A user is affected if their Raonwiz Raon K Upload version is 2018.0.2.51 or earlier, automatic updates are enabled, and the update module (web.js) lacks cryptographic integrity verification for downloaded updates.
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.
dbcve · scopedImplement cryptographic integrity verification (code signing/HMAC) for the update module before execution. If no patched version is available, disable automatic updates and manually manage updates from verified sources, or deploy network-level controls to restrict communication to trusted update servers.
Any version newer than 2018.0.2.51 (contact vendor for exact latest stable release)
- 1. Identify all systems running Raon K Upload version 2018.0.2.51 or earlier
- 2. Check the vendor's official website (www.raonwiz.com or through www.boho.or.kr) for the latest version of Raon K Upload
- 3. Upgrade Raon K Upload to the latest available version (any version after 2018.0.2.51 should contain the integrity check fix)
- 4. Verify the upgrade was successful by checking the application version
- 5. Review and monitor the update module (web.js) configuration to ensure integrity verification is enabled
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7808 — 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-7808 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