Skip to content
Fencer Intel
high 7.5

CVE-2018-12558 json

The parse() method in the Email::Address module through 1.909 for Perl is vulnerable to Algorithmic complexity on specially prepared input,…

published 8y ago modified 4mo ago also EUVD-2018-4518

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.6%
EPSS 2.6% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

The parse() method in the Email::Address module through 1.909 for Perl is vulnerable to Algorithmic complexity on specially prepared input, leading to Denial of Service. Prepared special input that caused this problem contained 30 form-field characters ("\f").

Patch / fix

  • libemail-address-perl Debian 14, Debian 13, Debian 12 1.912-1

debian advisories DEBIAN-CVE-2018-12558

  • perl-Email-Address openSUSE Tumbleweed 1.913-1.1
  • perl-Email-Address Package Hub 15, openSUSE Leap 15.0 1.912-bp150.3.3.1

opensuse advisories openSUSE-SU-2024:12651-1openSUSE-SU-2019:1114-1

  • perl-email-address Alpine 3.24, Alpine 3.23, Alpine 3.22 +15 more 1.912-r0

alpine advisories ALPINE-CVE-2018-12558

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • perl-email-address Arch Linux 1.912-1

arch linux advisories AVG-722

Is CVE-2018-12558 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-2018-12558 updated cvss 7.5

perl-Email-Address: Specially crafted input could cause Denial of Service due to complex parse() method

  • Red Hat Enterprise Linux 7 perl-Email-Address
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 8 perl-Email-Address
    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

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

CVSS scores

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

Classification

Weakness
  • CWE-407 Inefficient Algorithmic Complexity

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.