dbcve.org
Captiva EinputApplication · Emc

CVE-2011-1744

MEDIUM · 5.8 CVSS v2.0 Published 2011-08-01
Fix available
A fix is available. Upgrade to 2.1.1.37 or later.
See remediation →
67/100
Remediation priority · Elevated
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
EMC Captiva eInput 2.1.1 before 2.1.1.37 does not restrict the origin of calls to ActiveX functions, which allows remote attackers to read arbitrary files or cause a denial of service via a crafted web site.

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

EMC Captiva eInput 2.1.1 ActiveX control lacks origin restrictions on its exported functions, allowing any webpage to invoke these functions without proper validation. This Same-Origin Policy bypass enables remote attackers to read arbitrary files accessible to the ActiveX control or trigger denial-of-service conditions by calling functions with crafted parameters.

MitigationUpgrade to EMC Captiva eInput 2.1.1.37 or later which contains the vendor patch. Alternatively, disable the ActiveX control in Internet Explorer security settings or deploy ActiveX killbits via Group Policy until patching is feasible.

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
Captiva EinputApplication
Affected:< 2.1.1.37

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
M
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:N/A:P

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 EMC Captiva eInput ActiveX control on the system
    Search for the ActiveX control DLL file. Common locations include C:\Program Files\EMC\Captiva eInput\ or C:\Program Files (x86)\EMC\Captiva eInput\. Look for files such as einput*.dll, eInputActiveX.dll, or similar. Also check Windows\System32 for any captiva-related DLLs.
    Affected if The ActiveX control DLL is present on the system
  2. Check the installed version of EMC Captiva eInput
    Open the Windows Control Panel, go to Programs and Features (or Add/Remove Programs), and locate 'EMC Captiva eInput' or 'Captiva eInput' in the list of installed software. Note the version number shown in the Version column. Alternatively, right-click the control DLL file and select Properties > Details to view the File Version.
    Affected if The installed version is lower than 2.1.1.37 (for example, 2.1.1, 2.1.0, or any version below 2.1.1.37)
  3. Verify the ActiveX control is registered in Windows
    Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Code Store Database\Distribution Units\ (for system-wide) or HKCU\SOFTWARE\Microsoft\Code Store Database\Distribution Units\ (for current user). Search for keys containing 'eInput', 'Captiva', or the CLSID of the control. You can also check HKCR\CLSID for registered COM objects related to Captiva.
    Affected if The ActiveX control CLSID is registered in the Windows registry
  4. Confirm ActiveX controls are enabled in Internet Explorer
    Open Internet Explorer, go to Tools > Internet Options > Security > Custom Level. In the Security Settings dialog, locate 'Run ActiveX controls and plugins' and check if it is set to Enable or Prompt. Also check 'Script ActiveX controls marked safe for scripting'.
    Affected if ActiveX controls are set to Enable or Prompt in Internet Explorer security settings

The environment is affected if EMC Captiva eInput version is below 2.1.1.37, the ActiveX control DLL is present and registered, and ActiveX is enabled in the browser, allowing untrusted web pages to invoke the control's functions.

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 2.1.1.37 or later
Fixed in 2.1.1.37
Interim mitigation

Upgrade to EMC Captiva eInput 2.1.1.37 or later which contains the vendor patch. Alternatively, disable the ActiveX control in Internet Explorer security settings or deploy ActiveX killbits via Group Policy until patching is feasible.

Fix this in Captiva Einput Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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