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

> Attackers can execute arbitrary code by providing source code with a long invalid data type to the Progress 4GL Compiler.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-q554-wwwv-mpv6

## What is CVE-2003-0485?

CVE-2003-0485 is a medium-severity memory corruption vulnerability in n/a, published on 28 Jun 2003. 

### Official description

Buffer overflow in Progress 4GL Compiler 9.1D06 and earlier allows attackers to execute arbitrary code via source code containing a long, invalid data type.

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

It affects 1 product.


Products: Progress 4gl Compiler.

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

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

## Is CVE-2003-0485 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0485 is a medium-severity memory corruption vulnerability in n/a, published on 28 Jun 2003. 
Exploitation: There is no known exploitation of CVE-2003-0485 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-0485/ (Markdown: https://insights.sbomify.com/CVE-2003-0485/index.md)
```

## Sources

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

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