dbcve.org
E3Application · Elipse

CVE-2015-0978

MEDIUM · 6.9 CVSS v2.0 Published 2015-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Multiple untrusted search path vulnerabilities in (1) EQATEC.Analytics.Monitor.Win32_vc100.dll and (2) EQATEC.Analytics.Monitor.Win32_vc100-x64.dll in Elipse E3 4.5.232 through 4.6.161 allow local users to gain privileges via a Trojan horse DLL in an unspecified directory. NOTE: this may overlap CVE-2015-2264.

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

Elipse E3 versions 4.5.232 through 4.6.161 contain untrusted search path vulnerabilities in EQATEC.Analytics.Monitor.Win32_vc100.dll and its x64 counterpart. The application loads these DLLs from directories that can be controlled by local users, enabling privilege escalation via DLL hijacking where a malicious DLL placed in a search path gets loaded with the application's privileges.

MitigationUpgrade Elipse E3 to a version newer than 4.6.161 to obtain patched DLLs, or remove the vulnerable EQATEC DLL files if unused, and ensure the application directory and related paths are not writable by unprivileged users.

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
E3Application
Affected:= 4.5= 4.6

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
Local
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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. Verify Elipse E3 installation and version
    Locate the Elipse E3 installation directory and check the version information, typically found in the main executable or via 'Add/Remove Programs' in the Windows Control Panel. Compare the installed version against the affected range of 4.5.232 through 4.6.161.
    Affected if The installed version falls within 4.5.232 to 4.6.161 inclusive, or is any version in the 4.5.x or 4.6.x line before 4.6.162.
  2. Locate vulnerable EQATEC DLL files
    Search the Elipse E3 installation directory for the files EQATEC.Analytics.Monitor.Win32_vc100.dll and EQATEC.Analytics.Monitor.x64_vc100.dll (or similar x64 naming). These DLLs are typically found in the application bin or installation root folder.
    Affected if Either or both EQATEC DLL files exist within the Elipse E3 installation directory.
  3. Check directory permissions on the application folder
    Right-click the Elipsis E3 installation directory, select Properties, then the Security tab. Verify which users have Write or Modify permissions on the folder and subfolders.
    Affected if Unprivileged users (non-admin) have Write or Modify permissions to the Elipse E3 installation directory, allowing them to place a malicious DLL.
  4. Check search path accessibility for DLL loading
    Examine directories in the DLL search path used by Elipse E3, including the application directory, system directories, and any user-writable folders in the PATH. Identify if any of these are world-writable or writable by non-admin users.
    Affected if Any directory in Elipse E3's DLL search path is writable by unprivileged users, enabling DLL hijacking.

You are affected if Elipse E3 version 4.5.232 through 4.6.161 is installed with the EQATEC DLLs present and any application directory or DLL search path location is writable by unprivileged users.

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

Upgrade Elipse E3 to a version newer than 4.6.161 to obtain patched DLLs, or remove the vulnerable EQATEC DLL files if unused, and ensure the application directory and related paths are not writable by unprivileged users.

Fix this in E3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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