# CVE-2007-2820: Memory corruption in n/a

> Remote attackers can execute arbitrary code via stack-based buffer overflows in the KSign ActiveX control, requiring user interaction to visit a malicious page.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** 22 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pp9g-j95w-j9r8

## What is CVE-2007-2820?

CVE-2007-2820 is a high-severity memory corruption vulnerability in n/a, published on 22 May 2007. 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

Multiple stack-based buffer overflows in the KSign KSignSWAT ActiveX Control (AxKSignSWAT.dll) 2.0.3.3 allow remote attackers to execute arbitrary code via long arguments to the (1) SWAT_Init, (2) SWAT_InitEx, (3) SWAT_InitEx2, (4) SWAT_InitEx3, and (5) SWAT_Login functions.

## Which versions are affected by CVE-2007-2820?

It affects 1 product.


Products: Ksign Ksignswat.

## How do I fix CVE-2007-2820?

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

## Is CVE-2007-2820 being exploited?

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

Public exploit code:

- KSign KSignSWAT 2.0.3.3 - ActiveX Control Remote Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2820 and fix it if it is affected.

What it is: CVE-2007-2820 is a high-severity memory corruption vulnerability in n/a, published on 22 May 2007. 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-2007-2820 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-2007-2820/ (Markdown: https://insights.sbomify.com/CVE-2007-2820/index.md)
```

## Sources

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

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