| Summary: | libvpx new security issues CVE-2019-9232, CVE-2019-9325, CVE-2019-9433 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | Sec team <security> |
| Severity: | normal | ||
| Priority: | Normal | CC: | cjw, zombie.ryushu |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA7TOO | ||
| Source RPM: | libvpx-1.8.1-2.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2019-11-09 15:14:42 CET
David Walser
2019-11-09 15:14:51 CET
Whiteboard:
(none) =>
MGA7TOO The fixes are actually in Android, not Chromium. Looking at upstream git tags I get the following: CVE-2019-9325 included in libvpx v1.8.1 so fixed in cauldron included in libvpx v1.8.0 so fixed in mga7 CVE-2019-9232 included in libvpx v1.8.1 so fixed in cauldron included in libvpx v1.8.0 so fixed in mga7 CVE-2019-9433 included in libvpx v1.8.1 so fixed in cauldron included in libvpx v1.8.0 so fixed in mga7 CC:
(none) =>
cjw Thanks! Resolution:
(none) =>
INVALID |