CVE-2020-7880
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 · uneditedThe vulnerabilty was discovered in ActiveX module related to NeoRS remote support program. This issue allows an remote attacker to download and execute remote file. It is because of improper parameter validation of StartNeoRS function in ActiveX.
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 confidenceCVE-2020-7880 is an ActiveX vulnerability in the NeoRS remote support program where the StartNeoRS function lacks proper parameter validation. This allows remote attackers to supply malicious parameters that cause the control to download and execute arbitrary remote files, achieving remote code execution on affected systems.
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<= rs10CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Verify if Douzone Neors is installedCheck installed programs for 'Douzone Neors' or 'NeoRS' in Add/Remove Programs (appwiz.cpl) or check common installation directories such as C:\Program Files\Douzone or C:\Program Files (x86)\DouzoneAffected if Douzone Neors is present on the system
-
Determine the installed versionRight-click the NeoRS application executable or DLL, select Properties, and check the File Version. Alternatively, check the version info within the program itself or in the installation directory for a file named something like 'rs.exe' or similar executableAffected if The version is rs10 or lower (or the version cannot be determined but Neors is present)
-
Confirm the ActiveX control is registeredSearch the Windows registry for entries containing 'NeoRS' or the ActiveX CLSID under HKLM\SOFTWARE\Microsoft\Code Store Database\DOMIGATION or HKCR\CLSID. Use 'regedit' or the command 'reg query HKCR /s /f NeoRS' to searchAffected if The NeoRS ActiveX control is registered in the Windows registry
-
Check if the ActiveX control is enabled in Internet ExplorerOpen Internet Explorer (if available), go to Internet Options > Security > Custom Level, and look for 'ActiveX controls and plugins' settings. Also check for the specific NeoRS control in IE's Manage Add-ons dialogAffected if The NeoRS ActiveX control is enabled or set to prompt/enabled for the relevant zones
A system is affected if it has Douzone Neors version rs10 or lower installed with the NeoRS ActiveX control present and enabled, allowing the StartNeoRS function to be invoked with malicious parameters.
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 NeoRS ActiveX control until a patched version is available. If the control is required, implement strict whitelist-based parameter validation on the StartNeoRS function to ensure only legitimate values are accepted.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7880 — 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-7880 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