# CVE-2001-0482: Privilege escalation in n/a

> Root users can bypass access controls to execute arbitrary commands or cause denial of service by modifying kernel variables via sysctl.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7hvg-572p-33pg

## What is CVE-2001-0482?

CVE-2001-0482 is a high-severity vulnerability in n/a, published on 18 Sep 2001. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Configuration error in Argus PitBull LX allows root users to bypass specified access control restrictions and cause a denial of service or execute arbitrary commands by modifying kernel variables such as MaxFiles, MaxInodes, and ModProbePath in /proc/sys via calls to sysctl.

## Which versions are affected by CVE-2001-0482?

It affects 1 product.


Products: Argus Systems Pitbull Lx.

## How do I fix CVE-2001-0482?

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

## Is CVE-2001-0482 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0482 and fix it if it is affected.

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

## Sources

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

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