# CVE-2013-0725: Other in ER Viewer

> Uncontrolled search path in ERDAS ER Viewer allows arbitrary code execution via malicious DLLs.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pcpx-g3r4-wv44

## What is CVE-2013-0725?

CVE-2013-0725 is a high-severity vulnerability in ERDAS ER Viewer, published on 30 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

ERDAS ER Viewer 13.0 has dwmapi.dll and irml.dll libraries arbitrary code execution vulnerabilities

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2013-0725?

It affects 1 product.


Products: Hexagongeospatial Erdas Er Viewer.

## How do I fix CVE-2013-0725?

No fix has been published for CVE-2013-0725 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-0725 being exploited?

There is no known exploitation of CVE-2013-0725 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0725 and fix it if it is affected.

What it is: CVE-2013-0725 is a high-severity vulnerability in ERDAS ER Viewer, published on 30 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-0725 in the wild and no public exploit code.

Affected product: ERDAS ER Viewer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-0725/ (Markdown: https://insights.sbomify.com/CVE-2013-0725/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-0725
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-0725
- OSV: https://osv.dev/vulnerability/CVE-2013-0725

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-0725/
Summaries are generated and may contain mistakes; the official description above is the record.