CVE-2022-23763
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 · uneditedOrigin validation error vulnerability in NeoRS’s ActiveX moudle allows attackers to download and execute arbitrary files. Remote attackers can use this vulerability to encourage users to access crafted web pages, causing damage such as malicious code infections.
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 · high confidenceThis is an origin validation error in NeoRS's ActiveX control where the component fails to properly validate the origin of requests, allowing remote attackers to trick the browser into making unauthorized requests that download and execute arbitrary files on the victim's system through the vulnerable ActiveX module.
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< 2021.3.10.1CVSS 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.
-
Confirm Douzone Neors installationLocate and inspect the installed Douzone Neors application on the system; check program files, installation directories, or use system inventory tools to find the software and its version informationAffected if The installed version is lower than 2021.3.10.1 (the version number shown is below the fixed release)
-
Identify NeoRS ActiveX component presenceSearch for the NeoRS ActiveX control file (.ocx or .dll) on the system; check common ActiveX registration locations or the application's installation directory for the vulnerable componentAffected if The NeoRS ActiveX control file exists on the system and is a version affected by this vulnerability
-
Verify browser ActiveX enablementCheck browser security settings (Internet Explorer legacy settings or browser-specific ActiveX controls list) to determine whether the NeoRS ActiveX control is allowed to runAffected if The NeoRS ActiveX control is enabled or set to run in browser settings, making exploitation possible
-
Compare installed version to affected rangeOnce the exact version of Douzone Neors is determined, compare it against the affected range: versions prior to 2021.3.10.1 are vulnerableAffected if The installed Douzone Neors version falls below 2021.3.10.1
A user is affected if the NeoRS ActiveX control is present and enabled, and the installed Douzone Neors version is below 2021.3.10.1.
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 data2021.3.10.1
Disable or remove the vulnerable NeoRS ActiveX control if possible; otherwise, implement strict origin validation checks in the ActiveX control's request handling logic and block ActiveX execution in browsers.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23763 — 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-2022-23763 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