# CVE-2000-0537: Path traversal in n/a

> Local attackers can append data to arbitrary files via the BRUEXECLOG environment variable, potentially compromising system integrity.

- **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:** 13 Oct 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-q4v2-vr66-2qp6

## What is CVE-2000-0537?

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

### Official description

BRU backup software allows local users to append data to arbitrary files by specifying an alternate configuration file with the BRUEXECLOG environmental variable.

## Which versions are affected by CVE-2000-0537?

It affects 1 product.


Products: Tolis Group Bru.

## How do I fix CVE-2000-0537?

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

## Is CVE-2000-0537 being exploited?

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

Public exploit code:

- BRU 15.1/16.0 - BRUEXECLOG Environment Variable (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-0583](https://insights.sbomify.com/CVE-2003-0583/): Memory corruption in n/a (high 7.2)
- [CVE-2003-0584](https://insights.sbomify.com/CVE-2003-0584/): Memory corruption in n/a (high 7.2)
- [CVE-2002-0210](https://insights.sbomify.com/CVE-2002-0210/): Path traversal in n/a (high 7.2)
- [CVE-2002-1512](https://insights.sbomify.com/CVE-2002-1512/): Path traversal in n/a (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0537 and fix it if it is affected.

What it is: CVE-2000-0537 is a high-severity path traversal vulnerability in n/a, published on 13 Oct 2000. 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-2000-0537 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-2000-0537/ (Markdown: https://insights.sbomify.com/CVE-2000-0537/index.md)
```

## Sources

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

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