Bug 1660525 (CVE-2018-19935) - CVE-2018-19935 php: NULL pointer dereference in ext/imap/php_imap.c resulting in a denial of service
Summary: CVE-2018-19935 php: NULL pointer dereference in ext/imap/php_imap.c resulting...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-19935
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1660526 1660864
Blocks: 1660528
TreeView+ depends on / blocked
 
Reported: 2018-12-18 14:42 UTC by Andrej Nemec
Modified: 2023-03-24 14:26 UTC (History)
4 users (show)

Fixed In Version: php 5.6.39, php 7.0.33, php 7.3.0
Clone Of:
Environment:
Last Closed: 2021-10-27 03:21:40 UTC
Embargoed:


Attachments (Terms of Use)

Description Andrej Nemec 2018-12-18 14:42:51 UTC
ext/imap/php_imap.c in PHP 5.x and 7.x before 7.3.0 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via an empty string in the message argument to the imap_mail function.

Upstream issue:

https://bugs.php.net/bug.php?id=77020

Upstream patch:

http://git.php.net/?p=php-src.git;a=commit;h=7edc639b9ff1c3576773d79d016abbeed1f93846

Comment 1 Andrej Nemec 2018-12-18 14:42:59 UTC
Created php tracking bugs for this issue:

Affects: fedora-all [bug 1660526]

Comment 2 Tomas Hoger 2018-12-18 21:29:51 UTC
This can not affect PHP packages provided for Red Hat Enterprise Linux 7, either directly via Red Hat Enterprise Linux 7, or via Red Hat Software Collections for Red Hat Enterprise Linux 7, as those packages do not include the affected imap extension.

In Red Hat Enterprise Linux 6, the php-imap package providing the imap extension is only distributed via the unsupported Optional repository.  The php-imap packages included in the Red Hat Software Collections for Red Hat Enterprise Linux 6 depend on the libc-client packages, which is only distributed via the unsupported Optional repository.


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