# CVE-2018-6461: Other in n/a

> Local attackers can gain privileges by placing malicious DLLs in the working directory, affecting March Hare WINCVS and CVS Suite users.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 5 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xqj3-xhhm-rh7c

## What is CVE-2018-6461?

CVE-2018-6461 is a high-severity vulnerability in n/a, published on 5 Feb 2018. 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

March Hare WINCVS before 2.8.01 build 6610, and CVS Suite before 2009R2 build 6610, contains an Insecure Library Loading vulnerability in the wincvs2.exe or wincvs.exe file, which may allow local users to gain privileges via a Trojan horse Python or TCL DLL file in the current working directory.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2018-6461?

It affects 1 product.


Products: March-Hare Wincvs.

## How do I fix CVE-2018-6461?

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

## Is CVE-2018-6461 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6461 and fix it if it is affected.

What it is: CVE-2018-6461 is a high-severity vulnerability in n/a, published on 5 Feb 2018. 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-2018-6461 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-2018-6461/ (Markdown: https://insights.sbomify.com/CVE-2018-6461/index.md)
```

## Sources

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

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