Skip to content
Fencer Intel
medium 5.0

CVE-2013-0238 json

The try_parse_v4_netmask function in hostmask.c in IRCD-Hybrid before 8.0.6 does not properly validate masks, which allows remote attackers…

published 13y ago modified 4mo ago also EUVD-2013-0271

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

Summary

The try_parse_v4_netmask function in hostmask.c in IRCD-Hybrid before 8.0.6 does not properly validate masks, which allows remote attackers to cause a denial of service (crash) via a mask that causes a negative number to be parsed.

Patch / fix

  • ircd-hybrid Debian 13, Debian 12 1:7.2.2.dfsg.2-10

debian advisories DEBIAN-CVE-2013-0238

Is CVE-2013-0238 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-2013-0238 updated cvss 5.0

ircd-hybrid: DoS due to not validating input when parsing masks

  • 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. Published
  2. First public exploit (EDB-24951)

Exploit prediction

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

Exploits and checks

  • EDB-24951 ircd-hybrid 8.0.5 - Denial of Service dos, 2013-04-12

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-20 Improper Input Validation

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.