# CVE-2006-5139: Denial of service in n/a

> Remote attackers can corrupt website content and potentially cause other impacts by sending a long message affecting Tables in MkPortal.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 2 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h484-3rpg-f8cm

## What is CVE-2006-5139?

CVE-2006-5139 is a medium-severity denial of service vulnerability in n/a, published on 2 Oct 2006. It can be exploited over the network.

### Official description

Unspecified vulnerability in MkPortal allows remote attackers to corrupt web site content, and possibly have other impact, via a certain long Message that affects "Tables," related to the Urlobox.

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

It affects 1 product.


Products: Mkportal Mkportal.

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

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

## Is CVE-2006-5139 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0194](https://insights.sbomify.com/CVE-2007-0194/): Information disclosure in n/a (high 7.8)
- [CVE-2007-6467](https://insights.sbomify.com/CVE-2007-6467/): SQL injection in n/a (high 7.5)
- [CVE-2007-3814](https://insights.sbomify.com/CVE-2007-3814/): SQL injection in n/a (high 7.5)
- [CVE-2007-3637](https://insights.sbomify.com/CVE-2007-3637/): SQL injection in n/a (high 7.5)
- [CVE-2007-0192](https://insights.sbomify.com/CVE-2007-0192/): Cross-site request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5139 is a medium-severity denial of service vulnerability in n/a, published on 2 Oct 2006. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2006-5139 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-2006-5139/ (Markdown: https://insights.sbomify.com/CVE-2006-5139/index.md)
```

## Sources

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

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