# CVE-2010-3377: Path traversal in n/a

> Local attackers can gain privileges by placing a malicious shared library in the current working directory due to unsafe LD_LIBRARY_PATH settings in SALOME scripts.

- **Severity:** Medium 6.9 (`AV:L/AC:M/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:** 20 Oct 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-r2xr-xwqf-wh8q

## What is CVE-2010-3377?

CVE-2010-3377 is a medium-severity path traversal vulnerability in n/a, published on 20 Oct 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The (1) runSalome, (2) runTestMedCorba, (3) runLightSalome, and (4) hxx2salome scripts in SALOME 5.1.3 place a zero-length directory name in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse shared library in the current working directory.

## Which versions are affected by CVE-2010-3377?

It affects 1 product.


Products: Salome-Platform Salome.

## How do I fix CVE-2010-3377?

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

## Is CVE-2010-3377 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3377 and fix it if it is affected.

What it is: CVE-2010-3377 is a medium-severity path traversal vulnerability in n/a, published on 20 Oct 2010. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-3377 in the wild and no public exploit code.

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-2010-3377/ (Markdown: https://insights.sbomify.com/CVE-2010-3377/index.md)
```

## Sources

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

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