CVE-2022-2294 Heap buffer overflow in WebRTC in Google Chrome prior to 103.0.5060.114 allowed a remote attacker to exploit heap corruption.

CVE-2017-5116 Mitigating factor: the attacker required user interaction (i.e. click on a web page). — at the time of disclosure, this issue had been reported by only a single user. CVE-2017-5117 Mitigating factor: the issue existed in only one configuration installation of the media plugin. — at the time of disclosure, this issue had been reported by only a single user. CVE-2017-5122 Mitigating factor: the issue was only triggered when a user visited a malicious site. — at the time of disclosure, this issue had been reported by only a single user. CVE-2017-5119 Mitigating factor: the issue existed in only one configuration installation of the media plugin. — at the time of disclosure, this issue had been reported by only a single user. CVE-2017-5120 Mitigating factor: the issue had a “low probability” of occurrence. — at the time of disclosure, this issue had been reported by only a single user. CVE-2017-5121 Mitigating factor: the issue was only triggered when a user visited a malicious site. — at the time of disclosure, this issue had been reported by only a single user. CVE-2017-5123 Mitigating factor: the issue was only triggered when a user visited a malicious site. — at the time of disclosure, this issue had been reported by only a single user. CVE-2017-5124 Mitigating factor:

Checklist item #4: What was the history of the development of the software?

CVE-2017-5120 Mitigating factor: the issue had a “low probability” of occurrence. — at the time of disclosure, this issue had been reported by only a single user.

Timeline

Published on: 07/28/2022 02:15:00 UTC
Last modified on: 08/04/2022 17:33:00 UTC

Checklist item #4: What was the history of the development of the software?

Timeline

References