# CVE-2001-1576: Memory corruption in n/a

> Local attackers can execute arbitrary code via a buffer overflow in the cron utility, potentially escalating privileges on Caldera UnixWare systems.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 5 Aug 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j28p-jv5c-wm63

## What is CVE-2001-1576?

CVE-2001-1576 is a medium-severity memory corruption vulnerability in n/a, published on 5 Aug 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in cron in Caldera UnixWare 7 allows local users to execute arbitrary code via a command line argument.

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

It affects 1 product.


Products: Caldera Unixware.

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

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

## Is CVE-2001-1576 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0246](https://insights.sbomify.com/CVE-2002-0246/): Memory corruption in n/a (high 7.2)
- [CVE-2001-1164](https://insights.sbomify.com/CVE-2001-1164/): Memory corruption in n/a (high 7.2)
- [CVE-2002-0105](https://insights.sbomify.com/CVE-2002-0105/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1576 is a medium-severity memory corruption vulnerability in n/a, published on 5 Aug 2005. 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-1576 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-1576/ (Markdown: https://insights.sbomify.com/CVE-2001-1576/index.md)
```

## Sources

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

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