# CVE-2006-1356: Memory corruption in n/a

> A stack-based buffer overflow in LibVC allows attackers to execute arbitrary code via a malicious vCard file, requiring user interaction to open the file.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-1356, GHSA-q25q-j6qv-cjrj

## What is CVE-2006-1356?

CVE-2006-1356 is a medium-severity memory corruption vulnerability in n/a, published on 22 Mar 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Stack-based buffer overflow in the count_vcards function in LibVC 3, as used in Rolo, allows user-assisted attackers to execute arbitrary code via a vCard file (e.g. contacts.vcf) containing a long line.

## Which versions are affected by CVE-2006-1356?

It affects 2 products.


Products: Andrew Hsu Libvc, Andrew Hsu Rolo.

## How do I fix CVE-2006-1356?

Upgrade to a fixed version.

## Is CVE-2006-1356 being exploited?

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

Public exploit code:

- LibVC - '.VCard' 003 Processing Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1356 and fix it if it is affected.

What it is: CVE-2006-1356 is a medium-severity memory corruption vulnerability in n/a, published on 22 Mar 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1356 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-2006-1356/ (Markdown: https://insights.sbomify.com/CVE-2006-1356/index.md)
```

## Sources

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

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