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

> Remote attackers can execute arbitrary code via a buffer overflow in HAURI ViRobot triggered by a long ViRobot_ID cookie.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2005-2671, GHSA-2qf6-qjgx-9hpj

## What is CVE-2005-2041?

CVE-2005-2041 is a medium-severity memory corruption vulnerability in n/a, published on 21 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in addschup in HAURI ViRobot 2.0, and possibly other products, allows remote attackers to execute arbitrary code via a long ViRobot_ID cookie (HTTP_COOKIE).

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

It affects 1 product.


Products: Hauri Virobot Linux Server.

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

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

## Is CVE-2005-2041 being exploited?

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

Public exploit code:

- ViRobot Advanced Server 2.0 - 'addschup' Remote Cookie (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2041 is a medium-severity memory corruption vulnerability in n/a, published on 21 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2041 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-2041/ (Markdown: https://insights.sbomify.com/CVE-2005-2041/index.md)
```

## Sources

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

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