Erdas Er ViewerApplication · Hexagongeospatial

CVE-2013-0725

HIGH · 7.8 CVSS v3.1 Published 2020-01-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
ERDAS ER Viewer 13.0 has dwmapi.dll and irml.dll libraries arbitrary code execution vulnerabilities

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

ERDAS ER Viewer 13.0 contains DLL hijacking vulnerabilities in dwmapi.dll and irml.dll libraries that allow arbitrary code execution. Attackers can exploit this by placing malicious versions of these DLLs in locations where the application searches for them, leading to execution of attacker-controlled code with the privileges of the running application.

MitigationIf a patched version is available, upgrade immediately. Otherwise, restrict or remove ERDAS ER Viewer 13.0 from systems until a fix is available, and ensure the application does not load DLLs from untrusted directories.

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
Erdas Er ViewerApplication
Affected:= 13.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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Confirm ERDAS ER Viewer installation and version
    Check if ERDAS ER Viewer version 13.0 is installed on the system. Look in standard installation directories (typically C:\Program Files\ERDAS ER Viewer or C:\Program Files (x86)\ERDAS ER Viewer) and check the version property of the executable erdas_er_viewer.exe or similar. Use system inventory or package management tools if available.
    Affected if ERDAS ER Viewer version 13.0 is installed on the system.
  2. Locate application directory and vulnerable DLLs
    Find the installation directory of ERDAS ER Viewer 13.0 and verify whether dwmapi.dll and/or irml.dll files are present in that directory. These are the DLLs identified as vulnerable to hijacking.
    Affected if dwmapi.dll or irml.dll exists in the ERDAS ER Viewer application directory, as these can be replaced with malicious versions.
  3. Check for DLL search path vulnerabilities
    Examine the application's DLL search order behavior. Determine if the application loads DLLs from the current working directory, user-controlled directories, or directories in the PATH environment variable that are writable by non-privileged users.
    Affected if The application loads DLLs from directories that are writable by untrusted users, enabling placement of malicious DLLs.
  4. Verify if application has been executed
    Check system logs, recent program executions, or the application's recent files/access timestamp to determine if ERDAS ER Viewer 13.0 has been launched. DLL hijacking occurs at runtime when the application loads the vulnerable DLLs.
    Affected if ERDAS ER Viewer 13.0 has been executed, as the DLL hijacking vulnerability is triggered when the application loads the vulnerable DLLs during runtime.

A system is affected if ERDAS ER Viewer version 13.0 is installed and either vulnerable DLLs exist in the application directory or the application loads DLLs from untrusted directories that could contain malicious DLLs.

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

If a patched version is available, upgrade immediately. Otherwise, restrict or remove ERDAS ER Viewer 13.0 from systems until a fix is available, and ensure the application does not load DLLs from untrusted directories.

Fix this in Erdas Er Viewer Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2013-0725 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