# CVE-2007-1057: Race condition in n/a

> Local attackers can exploit a race condition in the Nortel Net Direct client to replace files and execute arbitrary code when another user runs the client.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vgg4-3fcc-jh95

## What is CVE-2007-1057?

CVE-2007-1057 is a medium-severity vulnerability in n/a, published on 21 Feb 2007. 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

The Net Direct client for Linux before 6.0.5 in Nortel Application Switch 2424, VPN 3050 and 3070, and SSL VPN Module 1000 extracts and executes files with insecure permissions, which allows local users to exploit a race condition to replace a world-writable file in /tmp/NetClient and cause another user to execute arbitrary code when attempting to execute this client, as demonstrated by replacing /tmp/NetClient/client.

## Which versions are affected by CVE-2007-1057?

It affects 1 product.


Products: Nortel Net Direct Client.

## How do I fix CVE-2007-1057?

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

## Is CVE-2007-1057 being exploited?

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

Public exploit code:

- Nortel SSL VPN Linux Client 6.0.3 - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1057 and fix it if it is affected.

What it is: CVE-2007-1057 is a medium-severity vulnerability in n/a, published on 21 Feb 2007. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1057 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-2007-1057/ (Markdown: https://insights.sbomify.com/CVE-2007-1057/index.md)
```

## Sources

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

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