# 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.


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-4434, GHSA-hh46-vfhf-rqg7

## What is CVE-2012-4434?

CVE-2012-4434 is a high-severity vulnerability in fwknop, published on 9 Jan 2020. 

### Official description

fwknop before 2.0.3 allow remote authenticated users to cause a denial of service (server crash) or possibly execute arbitrary code.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Cipherdyne Fwknop.

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

Upgrade to a fixed version.

## Is CVE-2012-4434 being exploited?

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

## Other vulnerabilities in fwknop

- [CVE-2012-4436](https://insights.sbomify.com/CVE-2012-4436/): Memory corruption in n/a (medium 4.4)
- [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-4434 and fix it if it is affected.

What it is: CVE-2012-4434 is a high-severity vulnerability in fwknop, published on 9 Jan 2020. 
Exploitation: There is no known exploitation of CVE-2012-4434 in the wild and no public exploit code.

Affected product: fwknop. 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-4434/ (Markdown: https://insights.sbomify.com/CVE-2012-4434/index.md)
```

## Sources

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

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