Bug 1762519 (CVE-2019-13694) - CVE-2019-13694 chromium-browser: Use-after-free in WebRTC
Summary: CVE-2019-13694 chromium-browser: Use-after-free in WebRTC
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-13694
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: 1762526 1762527 1762528
Blocks: 1762531
TreeView+ depends on / blocked
 
Reported: 2019-10-16 21:10 UTC by kat
Modified: 2021-02-16 21:14 UTC (History)
4 users (show)

Fixed In Version: chromium-browser 77.0.3865.120
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-29 12:53:00 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3211 0 None None None 2019-10-29 09:28:55 UTC

Description kat 2019-10-16 21:10:20 UTC
An use-after-free flaw was found in the WebRTC component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=100525

External References:

https://chromereleases.googleblog.com/2019/10/stable-channel-update-for-desktop.html

Comment 1 kat 2019-10-16 21:13:22 UTC
Created chromium tracking bugs for this issue:

Affects: epel-7 [bug 1762528]
Affects: fedora-all [bug 1762527]

Comment 3 errata-xmlrpc 2019-10-29 09:28:54 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

Via RHSA-2019:3211 https://access.redhat.com/errata/RHSA-2019:3211

Comment 4 Product Security DevOps Team 2019-10-29 12:53:00 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-13694

Comment 5 Product Security DevOps Team 2019-10-29 18:52:35 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-13694


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