dbcve.org
ActivexApplication · Inogard

CVE-2019-19165

HIGH · 7.2 CVSS v3.1 Published 2020-04-29
Fix available
A fix is available. Upgrade to 1.0.5.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
AxECM.cab(ActiveX Control) in Inogard Ebiz4u contains a vulnerability that could allow remote files to be downloaded and executed by setting arguments to the activeX method. Download of Code Without Integrity Check vulnerability in ActiveX control of Inogard Co,,LTD Ebiz4u ActiveX of Inogard Co,,LTD(AxECM.cab) allows ATTACKER to cause a file download to Windows user's folder and execute. This issue affects: Inogard Co,,LTD Ebiz4u ActiveX of Inogard Co,,LTD(AxECM.cab) version 1.0.5.0 and later versions on windows 7/8/10.

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 confidence

The Inogard Ebiz4u AxECM.cab ActiveX control contains a method that allows remote files to be downloaded and executed without integrity verification. An attacker can exploit this by calling the ActiveX method with malicious arguments to download arbitrary code to a Windows user's folder and execute it, leading to remote code execution.

MitigationDisable or remove the vulnerable AxECM.cab ActiveX control in Internet Explorer and across the system. If the control is required for business functions, implement network-level controls to restrict communication to trusted sources and monitor for exploitation attempts.

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
ActivexApplication
Affected:< 1.0.5.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 the AxECM.cab ActiveX control file
    Search the system for the file AxECM.cab - check common ActiveX deployment directories such as C:\Windows\Downloaded Program Files\, or search using: dir /s /b AxECM.cab
    Affected if The file AxECM.cab exists on the system
  2. Determine the installed version of Inogard ActiveX
    Right-click the AxECM.cab file, select Properties, and check the File Version field under the Version tab. Compare this version number to the affected range of versions less than 1.0.5.0
    Affected if The file version is lower than 1.0.5.0
  3. Verify the ActiveX control is registered
    Open Windows Registry and check for the control under HKLM\SOFTWARE\Microsoft\Code Store Database\Distributed COM or HKCU\SOFTWARE\Classes\CLSID for entries containing AxECM or Inogard
    Affected if The control is registered in the Windows COM registry
  4. Check if the control is enabled in Internet Explorer
    Open Internet Explorer, go to Tools > Internet Options > Security > Custom Level, and look for Inogard AxECM or Ebiz4u ActiveX controls in the ActiveX controls and plugins list
    Affected if The ActiveX control is set to Enabled or Prompt (not Disabled)
  5. Inspect the control for the vulnerable method
    Use a COM object viewer (such as OLE-COM Object Viewer or a PowerShell script with Get-Object) to enumerate the methods of the AxECM control and look for download/execute methods that accept remote URLs as parameters
    Affected if The control exposes methods that accept remote file paths without integrity verification

A user is affected if the AxECM.cab ActiveX control is installed with a version lower than 1.0.5.0 and the control is registered and enabled on the system.

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
Upgrade available Upgrade to 1.0.5.0 or later
Fixed in 1.0.5.0
Interim mitigation

Disable or remove the vulnerable AxECM.cab ActiveX control in Internet Explorer and across the system. If the control is required for business functions, implement network-level controls to restrict communication to trusted sources and monitor for exploitation attempts.

Fix this in Activex Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-19165 — 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-19165 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