Skip to content
Fencer Intel
critical 9.8

CVE-2010-3438 json

libpoe-component-irc-perl before v6.32 does not remove carriage returns and line feeds.

published 6y ago modified 4mo ago also EUVD-2010-3436

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 76%
public exploits
0
none known

Summary

libpoe-component-irc-perl before v6.32 does not remove carriage returns and line feeds. This can be used to execute arbitrary IRC commands by passing an argument such as "some text\rQUIT" to the 'privmsg' handler, which would cause the client to disconnect from the server.

Patch / fix

  • libpoe-component-irc-perl_project libpoe-component-irc-perl 6.32
  • libpoe-component-irc-perl Debian 14, Debian 13, Debian 12 6.32+dfsg-1

debian advisories DEBIAN-CVE-2010-3438

Is CVE-2010-3438 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-3438 updated

perl-POE-Component-IRC: arbitrary IRC command execution due to insufficient stripping of CR/LF

  • 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

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • libpoe-component-irc-perl libpoe-component-irc-perl

Classification

Weakness
  • CWE-134 Use of Externally-Controlled Format String

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.