# CVE-2011-4221: Other in n/a

> Remote attackers can cause application crashes or execute arbitrary code by tricking users into opening a crafted document in Able2Doc.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 1 Nov 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7hmq-jcvc-j3gv

## What is CVE-2011-4221?

CVE-2011-4221 is a critical vulnerability in n/a, published on 1 Nov 2011. 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

Unspecified vulnerability in Investintech.com Able2Doc and Able2Doc Professional allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted document.

## Which versions are affected by CVE-2011-4221?

It affects 1 product.


Products: Investintech Able2doc.

## How do I fix CVE-2011-4221?

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

## Is CVE-2011-4221 being exploited?

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

Public exploit code:

- Slimpdf Reader 1.0 - Memory Corruption (exploitdb)
- Able2Extract and Able2Extract Server 6.0 - Memory Corruption (exploitdb)
- Able2Doc and Able2Doc Professional 6.0 - Memory Corruption (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4221 and fix it if it is affected.

What it is: CVE-2011-4221 is a critical vulnerability in n/a, published on 1 Nov 2011. An attacker can exploit it over the internet without logging in, 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-2011-4221 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-2011-4221/ (Markdown: https://insights.sbomify.com/CVE-2011-4221/index.md)
```

## Sources

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

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