Advisories ยป MGASA-2022-0057

Updated firefox packages fix security vulnerability

Publication date: 12 Feb 2022
Modification date: 12 Feb 2022
Type: security
Affected Mageia releases : 8
CVE: CVE-2022-22754 , CVE-2022-22756 , CVE-2022-22759 , CVE-2022-22760 , CVE-2022-22761 , CVE-2022-22763 , CVE-2022-22764

Description

If a user installed an extension of a particular type, the extension could
have auto-updated itself and while doing so, bypass the prompt which grants
the new version the new requested permissions (CVE-2022-22754).

If a user was convinced to drag and drop an image to their desktop or other
folder, the resulting object could have been changed into an executable script
which would have run arbitrary code after the user clicked on it
(CVE-2022-22756).

If a document created a sandboxed iframe without allow-scripts, and
subsequently appended an element to the iframe's document that e.g. had a
JavaScript event handler - the event handler would have run despite the
iframe's sandbox (CVE-2022-22759).

When importing resources using Web Workers, error messages would distinguish
the difference between application/javascript responses and non-script
responses. This could have been abused to learn information cross-origin
(CVE-2022-22760).

Web-accessible extension pages (pages with a moz-extension:// scheme) were not
correctly enforcing the frame-ancestors directive when it was used in the Web
Extension's Content Security Policy (CVE-2022-22761).

When a worker is shutdown, it was possible to cause script to run late in the
lifecycle, at a point after where it should not be possible (CVE-2022-22763).

Mozilla developers and community members Paul Adenot and the Mozilla Fuzzing
Team reported memory safety bugs present in Firefox ESR 91.5. 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
(CVE-2022-22764).

References

SRPMS

8/core