Bug 1788727 (CVE-2019-17024) - CVE-2019-17024 Mozilla: Memory safety bugs fixed in Firefox 72 and Firefox ESR 68.4
Summary: CVE-2019-17024 Mozilla: Memory safety bugs fixed in Firefox 72 and Firefox ES...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-17024
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1788028 1788029 1788030 1788031 1788032 1788033 1790248 1790249 1790250 1790251 1790252 1790253
Blocks: 1787590
TreeView+ depends on / blocked
 
Reported: 2020-01-07 22:37 UTC by Doran Moppert
Modified: 2020-02-06 02:48 UTC (History)
5 users (show)

Fixed In Version: firefox 68.4, thunderbird 68.4.1
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-13 20:09:37 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:0085 None None None 2020-01-13 14:38:49 UTC
Red Hat Product Errata RHSA-2020:0086 None None None 2020-01-13 14:19:47 UTC
Red Hat Product Errata RHSA-2020:0111 None None None 2020-01-14 18:39:04 UTC
Red Hat Product Errata RHSA-2020:0120 None None None 2020-01-16 11:58:00 UTC
Red Hat Product Errata RHSA-2020:0123 None None None 2020-01-16 11:50:15 UTC
Red Hat Product Errata RHSA-2020:0127 None None None 2020-01-16 12:53:01 UTC
Red Hat Product Errata RHSA-2020:0292 None None None 2020-01-30 09:02:29 UTC
Red Hat Product Errata RHSA-2020:0295 None None None 2020-01-30 10:02:39 UTC

Description Doran Moppert 2020-01-07 22:37:42 UTC
Mozilla developers Jason Kratzer, Christian Holler, and Bob Clary reported memory safety bugs present in Firefox 71 and Firefox ESR 68.3. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.



External Reference:

https://www.mozilla.org/en-US/security/advisories/mfsa2020-02/#CVE-2019-17024

Comment 1 Doran Moppert 2020-01-07 22:37:45 UTC
Acknowledgments:

Name: the Mozilla project
Upstream: Mozilla developers

Comment 2 errata-xmlrpc 2020-01-13 14:19:46 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2020:0086 https://access.redhat.com/errata/RHSA-2020:0086

Comment 3 errata-xmlrpc 2020-01-13 14:38:48 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2020:0085 https://access.redhat.com/errata/RHSA-2020:0085

Comment 4 Product Security DevOps Team 2020-01-13 20:09:37 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2019-17024

Comment 6 errata-xmlrpc 2020-01-14 18:39:03 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2020:0111 https://access.redhat.com/errata/RHSA-2020:0111

Comment 7 errata-xmlrpc 2020-01-16 11:50:13 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2020:0123 https://access.redhat.com/errata/RHSA-2020:0123

Comment 8 errata-xmlrpc 2020-01-16 11:57:58 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2020:0120 https://access.redhat.com/errata/RHSA-2020:0120

Comment 9 errata-xmlrpc 2020-01-16 12:52:59 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2020:0127 https://access.redhat.com/errata/RHSA-2020:0127

Comment 10 errata-xmlrpc 2020-01-30 09:02:28 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions

Via RHSA-2020:0292 https://access.redhat.com/errata/RHSA-2020:0292

Comment 11 errata-xmlrpc 2020-01-30 10:02:37 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions

Via RHSA-2020:0295 https://access.redhat.com/errata/RHSA-2020:0295


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