dbcve.org
Dext5Application · Raonwiz

CVE-2019-19169

CRITICAL · 9.8 CVSS v3.1 Published 2020-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Dext5.ocx ActiveX 5.0.0.116 and eariler versions contain a vulnerability, which could allow remote attacker to download 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 confidence

Dext5.ocx ActiveX control versions 5.0.0.116 and earlier contains an arbitrary file download vulnerability. Remote attackers can exploit this by supplying malicious arguments to the ActiveX method, allowing download of arbitrary files to the victim's system, which can be leveraged for code execution.

MitigationUpdate to a patched version of Dext5.ocx if available, otherwise apply kill bits or registry settings to disable the ActiveX control, or remove the software entirely from 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
Dext5Application
Affected:= 2.7

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Dext5.ocx file on the system
    Search for 'Dext5.ocx' using file search or command: dir /s C:\Dext5.ocx (adjust drive letter as needed)
    Affected if The file exists on the system, proceed to version check. If not found, the control may not be installed or may use a different filename.
  2. Get the installed version of Dext5.ocx
    Right-click the Dext5.ocx file, select Properties, then look at the Version tab. Alternatively, use PowerShell: (Get-Item 'C:\path\to\Dext5.ocx').VersionInfo
    Affected if The file version is 5.0.0.116 or earlier, or the version information cannot be retrieved (older/unpatched builds may lack proper version metadata).
  3. Check if the ActiveX control is registered in Windows Registry
    Search the registry for 'Dext5' under HKLM\SOFTWARE\Microsoft\Code Store Database\Component Storage or HKLM\SOFTWARE\Classes\CLSID. Also check HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\ModuleUsage for CLSID {E08805C1-3C55-4d3e-8A12-5C32775CCF88} or similar Dext5-related CLSIDs.
    Affected if The control has an active registry entry indicating it is registered and potentially usable by Internet Explorer or other applications.
  4. Verify if ActiveX is enabled in Internet Explorer
    In Internet Explorer, go to Internet Options > Security > Custom Level > ActiveX controls and plugins. Look for settings that allow ActiveX controls to run or prompt.
    Affected if ActiveX controls are permitted to run (not set to Disabled or Prompt) - this enables the attack surface.
  5. Check for recent usage or instantiation logs
    Review browser history, proxy logs, or endpoint detection logs for evidence of Dext5.ocx being loaded. Check Windows Event Viewer under Application logs for errors related to Dext5.
    Affected if Evidence exists of the control being loaded or instantiated, indicating active use in the environment.

A user is affected if Dext5.ocx is present on their system with version 5.0.0.116 or earlier AND the ActiveX control is registered and enabled, allowing potential exploitation of the arbitrary file download vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of Dext5.ocx if available, otherwise apply kill bits or registry settings to disable the ActiveX control, or remove the software entirely from affected systems.

Fix this in Dext5 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-19169 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-19169 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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