Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1593318 - (CVE-2018-12558) CVE-2018-12558 perl-Email-Address: Specially crafted input could cause Denial of Service due to complex parse() method
CVE-2018-12558 perl-Email-Address: Specially crafted input could cause Denial...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180619,repor...
: Security
Depends On: 1593319 1593320 1601806 1593321
Blocks: 1593323
  Show dependency treegraph
 
Reported: 2018-06-20 10:35 EDT by Andrej Nemec
Modified: 2018-07-24 18:55 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github Perl-Email-Project/Email-Address/issues/19 None None None 2018-06-21 02:45 EDT

  None (edit)
Description Andrej Nemec 2018-06-20 10:35:18 EDT
The parse() method in the Email::Address module through 1.909 for Perl can consume a large amount of resources on specially prepared input, leading to Denial of Service. Prepared special input that caused this problem contained 30 form-field characters ("\f").

References:

http://seclists.org/oss-sec/2018/q2/211
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901873
Comment 1 Andrej Nemec 2018-06-20 10:36:00 EDT
Created perl-Email-Address tracking bugs for this issue:

Affects: epel-6 [bug 1593320]
Affects: fedora-all [bug 1593319]
Comment 4 Tomas Hoger 2018-07-17 06:22:43 EDT
Upstream bug:

https://github.com/Perl-Email-Project/Email-Address/issues/19

Note You need to log in before you can comment on or make changes to this bug.