# CVE-2010-1677: Denial of service in n/a

> Remote attackers can cause denial of service via CPU consumption in MHonArc by sending nested start tags.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jan 2011
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-1677, GHSA-7jx8-cpc3-f4pq

## What is CVE-2010-1677?

CVE-2010-1677 is a medium-severity denial of service vulnerability in n/a, published on 3 Jan 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MHonArc 2.6.16 allows remote attackers to cause a denial of service (CPU consumption) via start tags that are placed within other start tags, as demonstrated by a <bo<bo<bo<bo<body>dy>dy>dy>dy> sequence, a different vulnerability than CVE-2010-4524.

Weakness: CWE-399

## Which versions are affected by CVE-2010-1677?

It affects 1 product.


Products: Mhonarc Mhonarc.

## How do I fix CVE-2010-1677?

Upgrade to a fixed version.

## Is CVE-2010-1677 being exploited?

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

Public exploit code:

- MHonArc 2.6.16 - Tag Nesting Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0738](https://insights.sbomify.com/CVE-2002-0738/): Cross-site scripting in n/a (high 7.5)
- [CVE-2002-1307](https://insights.sbomify.com/CVE-2002-1307/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2010-4524](https://insights.sbomify.com/CVE-2010-4524/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2002-1388](https://insights.sbomify.com/CVE-2002-1388/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1677 and fix it if it is affected.

What it is: CVE-2010-1677 is a medium-severity denial of service vulnerability in n/a, published on 3 Jan 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-1677 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-2010-1677/ (Markdown: https://insights.sbomify.com/CVE-2010-1677/index.md)
```

## Sources

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

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