CVE-2019-19168
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 · uneditedDext5.ocx ActiveX 5.0.0.116 and eariler versions contain a vulnerability, which could allow remote attacker to download and execute remote arbitrary file by setting the arguments to the activex method. This can be leveraged for code execution.
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 confidenceDext5.ocx ActiveX versions 5.0.0.116 and earlier contain a remote code execution vulnerability where attackers can supply arguments to an ActiveX method to download and execute arbitrary files on the victim's system, leading to complete system compromise.
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= 2.7CVSS 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.
-
Locate Dext5.ocx on the systemSearch for dext5.ocx file using: dir /s /b C:\dext5.ocx 2>nul or use Windows Search. Typical locations include Windows\System32, application program folders, or user-downloaded directories.Affected if Dext5.ocx file is found on the system
-
Get the file version of Dext5.ocxRight-click the dext5.ocx file, select Properties, go to the Details tab to view File Version. Alternatively use PowerShell: (Get-Item 'C:\path\to\dext5.ocx').VersionInfo.FileVersionAffected if Version is 5.0.0.116 or earlier, or version 2.7 or earlier (both version schemes may exist)
-
Check if Dext5 ActiveX control is enabled in Internet ExplorerOpen Internet Explorer, go to Settings > Manage Add-ons > Toolbars and Extensions. Look for 'Dext5' or 'Dext5.ocx' in the list and check its status.Affected if Dext5 ActiveX control appears enabled (Status is not 'Disabled')
-
Verify ActiveX control is not blocked via Group PolicyCheck Registry key HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\LowDefaultBlocking or search for Group Policy settings that disable ActiveX controls. Also check IE security zone settings for ActiveX controls.Affected if No Group Policy or registry blocking is configured for this control
System is affected if Dext5.ocx file exists at any version 5.0.0.116 or earlier (or 2.7 and earlier) AND the ActiveX control is not disabled or blocked.
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 dataUpgrade Dext5.ocx to a patched version if available; otherwise disable the ActiveX control via Internet Explorer add-on management or Group Policy, and consider network-level blocking of untrusted content delivery.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19168 — 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-2019-19168 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