dbcve.org
IntegraxorApplication · Ecava

CVE-2012-0246

HIGH · 9.3 CVSS v2.0 Published 2012-04-02
Fix available
A fix is available. Upgrade to after 3.60.4061 or later.
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
Directory traversal vulnerability in an unspecified ActiveX control in Ecava IntegraXor before 3.71.4200 allows remote attackers to execute arbitrary code via vectors involving an HTML document on the server.

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

Directory traversal vulnerability in an unspecified ActiveX control in Ecava IntegraXor (HMI/SCADA software) before version 3.71.4200 allows remote attackers to execute arbitrary code via crafted HTML documents on the server.

MitigationUpgrade to IntegraXor version 3.71.4200 or later to patch the vulnerable ActiveX control. If upgrading is not immediately feasible, disable or restrict access to the ActiveX control and implement network segmentation to limit exposure.

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
IntegraxorApplication
Affected:<= 3.60.4061= 3.5.3900.5= 3.5.3900.10= 3.6.4000.0= 3.60

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
Complete
Integrity
Complete
Availability
Complete

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

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. Check if Ecava IntegraXor is installed
    Look for the IntegraXor installation directory, typically under C:\Program Files\Ecava\IntegraXor or C:\IntegraXor. Also check Windows Registry under HKLM\SOFTWARE\Ecava or HKLM\SOFTWARE\WOW6432Node\Ecava for IntegraXor entries.
    Affected if The software is found installed on the system.
  2. Identify the installed IntegraXor version
    Check the version by opening the IntegraXor application, looking in the installation directory for a version file or executable properties, or querying the Windows Registry key HKLM\SOFTWARE\Ecava\IntegraXor\Version if present.
    Affected if The installed version matches any of these: <= 3.60.4061, 3.5.3900.5, 3.5.3900.10, 3.6.4000.0, or 3.60.
  3. Verify the ActiveX control is web-accessible
    Check if the IntegraXor web server is running and the ActiveX control (typically referenced as SafeX or similar ActiveX components in the web interface) is accessible via the web interface on the default port 80 or configured HTTP port. Access the web URL such as http://localhost/ and look for ActiveX object references in the HTML.
    Affected if The IntegraXor web server is running and serves ActiveX controls to clients.
  4. Inspect for HTML documents on the server
    Review HTML files stored in the IntegraXor web root directory (commonly found in the \web or \www subfolder within the installation directory) for suspicious script tags or parameters that could indicate exploitation attempts.
    Affected if Crafted HTML documents exist on the server that target the directory traversal vulnerability in the ActiveX control.

A user is affected if Ecava IntegraXor version 3.60 or below (including specific versions 3.5.3900.5, 3.5.3900.10, 3.6.4000.0, or 3.60.4061) is installed and the ActiveX control is web-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.60.4061
Interim mitigation

Upgrade to IntegraXor version 3.71.4200 or later to patch the vulnerable ActiveX control. If upgrading is not immediately feasible, disable or restrict access to the ActiveX control and implement network segmentation to limit exposure.

Recommended fix High confidence

Ecava IntegraXor version 3.71.4200 or later

  1. 1. Identify the current IntegraXor version by checking the application or system information
  2. 2. If the current version is 3.71.4200 or higher, the vulnerability is already patched
  3. 3. If the current version is lower than 3.71.4200 (including any 3.5.x, 3.6.x, or 3.60.x versions up to 3.60.4061), plan an upgrade to version 3.71.4200 or later
  4. 4. Obtain the fixed version 3.71.4200 or newer from the official Ecava website or authorized distribution channels
  5. 5. Test the new version in a non-production environment to verify functionality
  6. 6. Apply the upgrade to production systems
Caveat Review release notes for any configuration or compatibility changes between your current version and 3.71.4200+

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Integraxor Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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