# CVE-2005-1394: Memory corruption in n/a

> Local attackers can exploit a format string vulnerability in ArcGIS Workstation via environment variables to execute arbitrary code and escalate privileges.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fcmj-qrc7-5x9g

## What is CVE-2005-1394?

CVE-2005-1394 is a high-severity memory corruption vulnerability in n/a, published on 2 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Format string vulnerability in ArcGIS for ESRI ArcInfo Workstation 9.0 allows local users to gain privileges via format string specifiers in the ARCHOME environment variable to (1) wservice or (2) lockmgr.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2005-1394?

It affects 1 product.


Products: Esri Arcinfo Workstation.

## How do I fix CVE-2005-1394?

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

## Is CVE-2005-1394 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1394 exists.

Public exploit code:

- Solaris 10.x - ESRI Arcgis Format String Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-1393](https://insights.sbomify.com/CVE-2005-1393/): Memory corruption in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1394 and fix it if it is affected.

What it is: CVE-2005-1394 is a high-severity memory corruption vulnerability in n/a, published on 2 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1394 exists.

Affected product: n/a. 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-2005-1394/ (Markdown: https://insights.sbomify.com/CVE-2005-1394/index.md)
```

## Sources

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

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