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

> Remote attackers can execute arbitrary code via a buffer overflow in the Change Manager component of Sun Management Center.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-v9x2-jp3v-cvfx

## What is CVE-2003-1576?

CVE-2003-1576 is a critical memory corruption vulnerability in n/a, published on 28 Jan 2010. It can be exploited over the network, with no action from the victim.

### Official description

Buffer overflow in pamverifier in Change Manager (CM) 1.0 for Sun Management Center (SunMC) 3.0 on Solaris 8 and 9 on the sparc platform allows remote attackers to execute arbitrary code via unspecified vectors.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Sun Change Manager.

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

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

## Is CVE-2003-1576 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2003-1576 is a critical memory corruption vulnerability in n/a, published on 28 Jan 2010. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-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-2003-1576/ (Markdown: https://insights.sbomify.com/CVE-2003-1576/index.md)
```

## Sources

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

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