ALT-BU-2021-4246-1
Branch p9 update bulletin.
Package firefox-esr updated to version 78.14.0-alt0.p9.1 for branch p9 in task 284965.
Closed vulnerabilities
BDU:2021-04558
Уязвимость браузеров Mozilla Firefox, Firefox ESR и почтового клиента Thunderbird, связанная с выходом операции за границы буфера в памяти, позволяющая нарушителю выполнить произвольный код
Modified: 2024-11-21
CVE-2021-38492
When delegating navigations to the operating system, Firefox would accept the `mk` scheme which might allow attackers to launch pages and execute scripts in Internet Explorer in unprivileged mode. *This bug only affects Firefox for Windows. Other operating systems are unaffected.*. This vulnerability affects Firefox < 92, Thunderbird < 91.1, Thunderbird < 78.14, Firefox ESR < 78.14, and Firefox ESR < 91.1.
- https://bugzilla.mozilla.org/show_bug.cgi?id=1721107
- https://bugzilla.mozilla.org/show_bug.cgi?id=1721107
- GLSA-202208-14
- GLSA-202208-14
- https://www.mozilla.org/security/advisories/mfsa2021-38/
- https://www.mozilla.org/security/advisories/mfsa2021-38/
- https://www.mozilla.org/security/advisories/mfsa2021-39/
- https://www.mozilla.org/security/advisories/mfsa2021-39/
- https://www.mozilla.org/security/advisories/mfsa2021-40/
- https://www.mozilla.org/security/advisories/mfsa2021-40/
- https://www.mozilla.org/security/advisories/mfsa2021-41/
- https://www.mozilla.org/security/advisories/mfsa2021-41/
- https://www.mozilla.org/security/advisories/mfsa2021-42/
- https://www.mozilla.org/security/advisories/mfsa2021-42/
Modified: 2024-11-21
CVE-2021-38493
Mozilla developers reported memory safety bugs present in Firefox 91 and Firefox ESR 78.13. 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. This vulnerability affects Firefox ESR < 78.14, Thunderbird < 78.14, and Firefox < 92.
- https://bugzilla.mozilla.org/buglist.cgi?bug_id=1723391%2C1724101%2C1724107
- https://bugzilla.mozilla.org/buglist.cgi?bug_id=1723391%2C1724101%2C1724107
- GLSA-202202-03
- GLSA-202202-03
- GLSA-202208-14
- GLSA-202208-14
- https://www.mozilla.org/security/advisories/mfsa2021-38/
- https://www.mozilla.org/security/advisories/mfsa2021-38/
- https://www.mozilla.org/security/advisories/mfsa2021-39/
- https://www.mozilla.org/security/advisories/mfsa2021-39/
- https://www.mozilla.org/security/advisories/mfsa2021-42/
- https://www.mozilla.org/security/advisories/mfsa2021-42/
Closed vulnerabilities
BDU:2021-04686
Уязвимость функционала PreChecks эталонной реализации Bitcoin Bitcoin Core, связанная с неправильной авторизацией, позволяющая нарушителю нарушить целостность данных, а также вызвать отказ в обслуживании
Modified: 2024-11-21
CVE-2021-31876
Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the replacement policy specified in BIP125, which makes it easier for attackers to trigger a loss of funds, or a denial of service attack against downstream projects such as Lightning network nodes. An unconfirmed child transaction with nSequence = 0xff_ff_ff_ff, spending an unconfirmed parent with nSequence <= 0xff_ff_ff_fd, should be replaceable because there is inherited signaling by the child transaction. However, the actual PreChecks implementation does not enforce this. Instead, mempool rejects the replacement attempt of the unconfirmed child transaction.
- https://bitcoinops.org/en/newsletters/2021/05/12/
- https://bitcoinops.org/en/newsletters/2021/05/12/
- https://bitcoinops.org/en/topics/replace-by-fee/
- https://bitcoinops.org/en/topics/replace-by-fee/
- https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2021-31876
- https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2021-31876
- https://github.com/bitcoin/bitcoin
- https://github.com/bitcoin/bitcoin
- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-May/018893.html
- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-May/018893.html
Modified: 2024-11-21
CVE-2021-3195
bitcoind in Bitcoin Core through 0.21.0 can create a new file in an arbitrary directory (e.g., outside the ~/.bitcoin directory) via a dumpwallet RPC call. NOTE: this reportedly does not violate the security model of Bitcoin Core, but can violate the security model of a fork that has implemented dumpwallet restrictions