# CVE-2012-4436: Memory corruption in n/a

> Local attackers can trigger a buffer overflow in the fwknop client via crafted arguments, causing a crash or potentially executing arbitrary code.

- **Severity:** Medium 4.4 (`AV:L/AC:M/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:** Not needed
- **Fix available:** Yes
- **Published:** 22 Oct 2012
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2012-4436, GHSA-f5j9-5h8m-c8mw

## What is CVE-2012-4436?

CVE-2012-4436 is a medium-severity memory corruption vulnerability in n/a, published on 22 Oct 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in the run_last_args function in client/fwknop.c in fwknop before 2.0.3, when processing --last, might allow local users to cause a denial of service (client crash) and possibly execute arbitrary code via many .fwknop.run arguments.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2012-4436?

It affects 1 product.


Products: Cipherdyne Fwknop.

## How do I fix CVE-2012-4436?

Upgrade to a fixed version.

## Is CVE-2012-4436 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4434](https://insights.sbomify.com/CVE-2012-4434/): fwknop before 2.0.3 allow remote authenticated users to cause a denial of service (server crash) or possibly execute arbitrary code. (high 8.8)
- [CVE-2012-4435](https://insights.sbomify.com/CVE-2012-4435/): Denial of service in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4436 and fix it if it is affected.

What it is: CVE-2012-4436 is a medium-severity memory corruption vulnerability in n/a, published on 22 Oct 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-4436 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-2012-4436/ (Markdown: https://insights.sbomify.com/CVE-2012-4436/index.md)
```

## Sources

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

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