Skip to content
Fencer Intel
medium 5.0

CVE-2010-1677 json

MHonArc 2.6.16 allows remote attackers to cause a denial of service (CPU consumption) via start tags that are placed within other start tag…

published 15y ago modified 4mo ago also EUVD-2010-1697

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.8%
EPSS 8.8% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

  • mhonarc Debian 14, Debian 13, Debian 12 2.6.18-1

debian advisories DEBIAN-CVE-2010-1677

Is CVE-2010-1677 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-1677 updated cvss 5.0

mhonarc: remote DoS via certain tags

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-35478)
  2. Published

Exploit prediction

8.84% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-35478 MHonArc 2.6.16 - Tag Nesting Remote Denial of Service dos, 2010-12-21

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-399 Resource Management Errors

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.