From: engblom <engblom@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Arbitrary code execution in Mozilla products
Date: Thu, 31 Aug 2023 07:40:17 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45833@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
New issue by engblom on void-packages repository
https://github.com/void-linux/void-packages/issues/45833
Description:
### Is this a new report?
Yes
### System Info
*
### Package(s) Affected
firefox* thunderbird*
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
Multiple vulnerabilities in Mozilla products
URL: https://www.cisa.gov/news-events/alerts/2023/08/30/mozilla-releases-security-updates-firefox-and-firefox-esr
Classification: Important, Solution: Official Fix, Exploit Maturity: Not Defined, CVSSv3: None
CVEs: CVE-2023-4051, CVE-2023-4053, CVE-2023-4573, CVE-2023-4574, CVE-2023-4575, CVE-2023-4576, CVE-2023-4577, CVE-2023-4578, CVE-2023-4579, CVE-2023-4580, CVE-2023-4581, CVE-2023-4582, CVE-2023-4583, CVE-2023-4584, CVE-2023-4585 See also: https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-mozilla-products-could-allow-for-arbitrary-code-execution_2023-096
Multiple vulnerabilities have been discovered in Mozilla products, the most severe of which could allow for arbitrary code execution.
SYSTEMS AFFECTED:
Firefox ESR versions prior to 102.15
Firefox ESR versions prior to 115.2
Firefox versions prior to 117
Thunderbird versions prior to 102.15
Thunderbird versions prior to 115.2
### Expected behaviour
------------------
### Actual behaviour
-----------------
### Steps to reproduce
-------------
next reply other threads:[~2023-08-31 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 5:40 engblom [this message]
2023-09-05 10:34 ` [ISSUE] [CLOSED] " engblom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45833@inbox.vuxu.org \
--to=engblom@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).