# CVE-2005-2297: Memory corruption in n/a

> Remote authenticated users can execute arbitrary code via a stack-based buffer overflow in Sybase EAServer.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xjgr-r86j-v85p

## What is CVE-2005-2297?

CVE-2005-2297 is a medium-severity memory corruption vulnerability in n/a, published on 19 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Stack-based buffer overflow in TreeAction.do in Sybase EAServer 4.2.5 through 5.2 allows remote authenticated users to execute arbitrary code via a large javascript parameter.

## Which versions are affected by CVE-2005-2297?

It affects 1 product.


Products: Sybase Easerver.

## How do I fix CVE-2005-2297?

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

## Is CVE-2005-2297 being exploited?

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

Public exploit code:

- Sybase EAServer 5.2 Remote Stack Buffer Overflow (metasploit)
- Sybase EAServer 5.2 - Remote Stack Buffer Overflow (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-2474](https://insights.sbomify.com/CVE-2011-2474/): Path traversal in n/a (medium 5.0)
- [CVE-2002-1861](https://insights.sbomify.com/CVE-2002-1861/): Path traversal in n/a (medium 5.0)
- [CVE-2012-4340](https://insights.sbomify.com/CVE-2012-4340/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2006-1829](https://insights.sbomify.com/CVE-2006-1829/): Information disclosure in n/a (medium 4.0)
- [CVE-2006-2539](https://insights.sbomify.com/CVE-2006-2539/): Information disclosure in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2297 and fix it if it is affected.

What it is: CVE-2005-2297 is a medium-severity memory corruption vulnerability in n/a, published on 19 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2297 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-2005-2297/ (Markdown: https://insights.sbomify.com/CVE-2005-2297/index.md)
```

## Sources

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

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