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

> Attackers can execute arbitrary code by tricking users into entering long strings in ICQ name fields, requiring user interaction.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4hpw-h5hg-pjg7

## What is CVE-2005-3433?

CVE-2005-3433 is a medium-severity memory corruption vulnerability in n/a, published on 2 Nov 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in Mirabilis ICQ 2003a allows user-assisted attackers to execute arbitrary code by convincing a user to enter long strings into the First Name and Last Name fields.

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

It affects 1 product.


Products: Mirabilis Icq.

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

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

## Is CVE-2005-3433 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2329](https://insights.sbomify.com/CVE-2002-2329/): Denial of service in n/a (high 7.8)
- [CVE-2006-4662](https://insights.sbomify.com/CVE-2006-4662/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0235](https://insights.sbomify.com/CVE-2003-0235/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0236](https://insights.sbomify.com/CVE-2003-0236/): Integer overflow in n/a (high 7.5)
- [CVE-2003-0237](https://insights.sbomify.com/CVE-2003-0237/): Supply chain in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3433 is a medium-severity memory corruption vulnerability in n/a, published on 2 Nov 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-3433 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-2005-3433/ (Markdown: https://insights.sbomify.com/CVE-2005-3433/index.md)
```

## Sources

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

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