-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
=============================================================================
FreeBSD-SA-21:11.smap Security Advisory
The FreeBSD Project
Topic: SMAP bypass
Category: core
Module: amd64
Announced: 2021-05-26
Credits: I lost my dog if you see him please contact me at @m00nbsd.
Affects: FreeBSD 12.2 and later.
Corrected: 2021-05-26 19:18:54 UTC (stable/13, 13.0-STABLE)
2021-05-26 19:31:50 UTC (releng/13.0, 13.0-RELEASE-p1)
2021-05-26 19:30:31 UTC (stable/12, 12.2-STABLE)
2021-05-26 20:40:20 UTC (releng/12.2, 12.2-RELEASE-p7)
CVE Name: CVE-2021-29628
For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:https://security.FreeBSD.org/>.
I. Background
Supervisor Mode Access Prevention (SMAP) is a security feature
implemented by contemporary Intel and AMD CPUs. When enabled, it
ensures that accesses to user memory by the kernel trigger a page fault
and a subsequent kernel panic. This helps mitigate the security
implications of kernel bugs that permit an attacker to read from or
write to user memory from the kernel.
The kernel may legitimately need to copy data between userspace and the
kernel. To enable this, SMAP is temporarily disabled in the subroutines
which handle this copying, so only small, specially designated portions
of the kernel should be executed with SMAP disabled.
II. Problem Description
The FreeBSD kernel enables SMAP during boot when the CPU reports that
the SMAP capability is present. Subroutines such as copyin() and
copyout() are responsible for disabling SMAP around the sections of code
that perform user memory accesses.
Such subroutines must handle page faults triggered when user memory is
not mapped. The kernel's page fault handler checks the validity of the
fault, and if it is indeed valid it will map a page and resume copying.
If the fault is invalid, the fault handler returns control to a
trampoline which aborts the operation and causes an error to be
returned. In this second scenario, a bug in the implementation of SMAP
support meant that SMAP would remain disabled until the thread returns
to user mode.
III. Impact
This bug may be used to bypass the protections provided by SMAP for the
duration of a system call. It could thus be combined with other kernel
bugs to craft an exploit.
IV. Workaround
No workaround is available. On hardware that does not implement SMAP,
the bug is inconsequential as the mitigation does not exist in the first
place.
V. Solution
Upgrade your vulnerable system to a supported FreeBSD stable or
release / security branch (releng) dated after the correction date
and reboot.
Perform one of the following:
1) To update your vulnerable system via a binary patch:
Systems running a RELEASE version of FreeBSD on the amd64, i386, or
(on FreeBSD 13 and later) arm64 platforms can be updated via the
freebsd-update(8) utility:
# freebsd-update fetch
# freebsd-update install
# shutdown -r +10min "Rebooting for a security update"
2) To update your vulnerable system via a source code patch:
The following patches have been verified to apply to the applicable
FreeBSD release branches.
a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.
# fetch https://security.FreeBSD.org/patches/SA-21:11/smap.patch
# fetch https://security.FreeBSD.org/patches/SA-21:11/smap.patch.asc
# gpg --verify smap.patch.asc
b) Apply the patch. Execute the following commands as root:
# cd /usr/src
# patch < /path/to/patch
c) Recompile your kernel as described in
<URL:https://www.FreeBSD.org/handbook/kernelconfig.html> and reboot the
system.
VI. Correction details
This issue is corrected by the corresponding Git commit hash or Subversion
revision number in the following stable and release branches:
Branch/path Hash Revision
- -------------------------------------------------------------------------
stable/13/ 876ffe28796c stable/13-n245764
releng/13.0/ f32130a1955e releng/13.0-n244739
stable/12/ r369857
releng/12.2/ r369863
- -------------------------------------------------------------------------
For FreeBSD 13 and later:
Run the following command to see which files were modified by a
particular commit:
# git show --stat <commit hash>
Or visit the following URL, replacing NNNNNN with the hash:
<URL:https://cgit.freebsd.org/src/commit/?id=NNNNNN>
To determine the commit count in a working tree (for comparison against
nNNNNNN in the table above), run:
# git rev-list --count --first-parent HEAD
For FreeBSD 12 and earlier:
Run the following command to see which files were modified by a particular
revision, replacing NNNNNN with the revision number:
# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base
Or visit the following URL, replacing NNNNNN with the revision number:
<URL:https://svnweb.freebsd.org/base?view=revision&revision=NNNNNN>
VII. References
<URL:https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29628>
The latest revision of this advisory is available at
<URL:https://security.FreeBSD.org/advisories/FreeBSD-SA-21:11.smap.asc>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAmCu6vIACgkQ05eS9J6n
5cJagg//Yy30r/Dq2rgoY7p31CoF/jXDDqNEhqyJTcWoDY2M5THXBficHxWW68lE
YLfndQRgz4oT7QNgxgnW0PYa0iHLiNFxZoI8lOcILpvHereXy0gEvLVPCstY7NY9
+jZnY7seLfSH+Y+VS5sjXbveMSMxovKzpp1rOrHVxJK7YeGY7YDqsK9pQ8Jk+4pE
XlhOvhugL0qE4Fxj4qI5ClGmqDvyNXxlGWWwVtzZV2jYN1bdmZ0g88+HgJI1FcUr
E2KIk1XwVidhQC8GJk9v7D/Bg4nYdq59Dozv4tu9IFfPkV+xl3qbgtXN5qJ0bp+u
Y3NCEgq8Aoz60Xebulw1XBfvJFkLqUEthenYKtMSc9hN+QgAM9c9eQreRawTNezK
aUSl+hUt9D6oVHh1Ki+OIhAgF+pAKN+7ARfcn2Ot57/TNbO1T9/C5mMd/hhQOkyj
wJwj3nSLkUVQTNR9ntyyIj44XFRijtzG4foAJDuozfzC+hD82jSgXpCGnLwH6Gyx
n0yIM1LbDZWrvAJ9W+uQmGJ1nv12Tzt24cDCSQ+zJjuTNfCso3bQ9b/IrXomBAwp
waYpEOujzjaM7XdI9F4vb69XGX9mbKO67MoXgwlVowaRvVUBM0jAkaRo1gknF1sO
CXLuogbOomTHcutlBsXtF0FBphLFx7YA8w4jtWnjnFW7wBzZ5dQ=
=/4r7
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@freebsd.org"
Wednesday, May 26, 2021
您好 想和您洽谈合作
我是靖飞公司朱静，我看到贵公司的产品比较符合我公司的要求，想与你洽谈一下，我来此的目的是为了询问一下与贵公司建立合作关系的可能性，可以加一下我的微信：13962538785 电话也是这个
[USN-4968-1] LZ4 vulnerability
==========================================================================
Ubuntu Security Notice USN-4968-1
May 26, 2021
lz4 vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 21.04
- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
Summary:
LZ4 could be made to crash or run programs if it opened a specially crafted
file.
Software Description:
- lz4: Extremely fast compression algorithm
Details:
It was discovered that LZ4 incorrectly handled certain memory operations.
If a user or automated system were tricked into uncompressing a specially-
crafted LZ4 file, a remote attacker could use this issue to cause LZ4 to
crash, resulting in a denial of service, or possibly execute arbitrary
code.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 21.04:
liblz4-1 1.9.3-1ubuntu0.1
Ubuntu 20.10:
liblz4-1 1.9.2-2ubuntu0.20.10.1
Ubuntu 20.04 LTS:
liblz4-1 1.9.2-2ubuntu0.20.04.1
Ubuntu 18.04 LTS:
liblz4-1 0.0~r131-2ubuntu3.1
In general, a standard system update will make all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4968-1
CVE-2021-3520
Package Information:
https://launchpad.net/ubuntu/+source/lz4/1.9.3-1ubuntu0.1
https://launchpad.net/ubuntu/+source/lz4/1.9.2-2ubuntu0.20.10.1
https://launchpad.net/ubuntu/+source/lz4/1.9.2-2ubuntu0.20.04.1
https://launchpad.net/ubuntu/+source/lz4/0.0~r131-2ubuntu3.1
Ubuntu Security Notice USN-4968-1
May 26, 2021
lz4 vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 21.04
- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
Summary:
LZ4 could be made to crash or run programs if it opened a specially crafted
file.
Software Description:
- lz4: Extremely fast compression algorithm
Details:
It was discovered that LZ4 incorrectly handled certain memory operations.
If a user or automated system were tricked into uncompressing a specially-
crafted LZ4 file, a remote attacker could use this issue to cause LZ4 to
crash, resulting in a denial of service, or possibly execute arbitrary
code.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 21.04:
liblz4-1 1.9.3-1ubuntu0.1
Ubuntu 20.10:
liblz4-1 1.9.2-2ubuntu0.20.10.1
Ubuntu 20.04 LTS:
liblz4-1 1.9.2-2ubuntu0.20.04.1
Ubuntu 18.04 LTS:
liblz4-1 0.0~r131-2ubuntu3.1
In general, a standard system update will make all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4968-1
CVE-2021-3520
Package Information:
https://launchpad.net/ubuntu/+source/lz4/1.9.3-1ubuntu0.1
https://launchpad.net/ubuntu/+source/lz4/1.9.2-2ubuntu0.20.10.1
https://launchpad.net/ubuntu/+source/lz4/1.9.2-2ubuntu0.20.04.1
https://launchpad.net/ubuntu/+source/lz4/0.0~r131-2ubuntu3.1
[USN-4967-1] nginx vulnerability
==========================================================================
Ubuntu Security Notice USN-4967-1
May 26, 2021
nginx vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 21.04
- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
Summary:
nginx could be made to crash or run programs if it received specially
crafted network traffic.
Software Description:
- nginx: small, powerful, scalable web/proxy server
Details:
Luis Merino, Markus Vervier, and Eric Sesterhenn discovered that nginx
incorrectly handled responses to the DNS resolver. A remote attacker could
use this issue to cause nginx to crash, resulting in a denial of service,
or possibly execute arbitrary code.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 21.04:
nginx 1.18.0-6ubuntu8.2
nginx-common 1.18.0-6ubuntu8.2
nginx-core 1.18.0-6ubuntu8.2
nginx-extras 1.18.0-6ubuntu8.2
nginx-full 1.18.0-6ubuntu8.2
nginx-light 1.18.0-6ubuntu8.2
Ubuntu 20.10:
nginx 1.18.0-6ubuntu2.2
nginx-common 1.18.0-6ubuntu2.2
nginx-core 1.18.0-6ubuntu2.2
nginx-extras 1.18.0-6ubuntu2.2
nginx-full 1.18.0-6ubuntu2.2
nginx-light 1.18.0-6ubuntu2.2
Ubuntu 20.04 LTS:
nginx 1.18.0-0ubuntu1.2
nginx-common 1.18.0-0ubuntu1.2
nginx-core 1.18.0-0ubuntu1.2
nginx-extras 1.18.0-0ubuntu1.2
nginx-full 1.18.0-0ubuntu1.2
nginx-light 1.18.0-0ubuntu1.2
Ubuntu 18.04 LTS:
nginx 1.14.0-0ubuntu1.9
nginx-common 1.14.0-0ubuntu1.9
nginx-core 1.14.0-0ubuntu1.9
nginx-extras 1.14.0-0ubuntu1.9
nginx-full 1.14.0-0ubuntu1.9
nginx-light 1.14.0-0ubuntu1.9
In general, a standard system update will make all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4967-1
CVE-2021-23017
Package Information:
https://launchpad.net/ubuntu/+source/nginx/1.18.0-6ubuntu8.2
https://launchpad.net/ubuntu/+source/nginx/1.18.0-6ubuntu2.2
https://launchpad.net/ubuntu/+source/nginx/1.18.0-0ubuntu1.2
https://launchpad.net/ubuntu/+source/nginx/1.14.0-0ubuntu1.9
Ubuntu Security Notice USN-4967-1
May 26, 2021
nginx vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 21.04
- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
Summary:
nginx could be made to crash or run programs if it received specially
crafted network traffic.
Software Description:
- nginx: small, powerful, scalable web/proxy server
Details:
Luis Merino, Markus Vervier, and Eric Sesterhenn discovered that nginx
incorrectly handled responses to the DNS resolver. A remote attacker could
use this issue to cause nginx to crash, resulting in a denial of service,
or possibly execute arbitrary code.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 21.04:
nginx 1.18.0-6ubuntu8.2
nginx-common 1.18.0-6ubuntu8.2
nginx-core 1.18.0-6ubuntu8.2
nginx-extras 1.18.0-6ubuntu8.2
nginx-full 1.18.0-6ubuntu8.2
nginx-light 1.18.0-6ubuntu8.2
Ubuntu 20.10:
nginx 1.18.0-6ubuntu2.2
nginx-common 1.18.0-6ubuntu2.2
nginx-core 1.18.0-6ubuntu2.2
nginx-extras 1.18.0-6ubuntu2.2
nginx-full 1.18.0-6ubuntu2.2
nginx-light 1.18.0-6ubuntu2.2
Ubuntu 20.04 LTS:
nginx 1.18.0-0ubuntu1.2
nginx-common 1.18.0-0ubuntu1.2
nginx-core 1.18.0-0ubuntu1.2
nginx-extras 1.18.0-0ubuntu1.2
nginx-full 1.18.0-0ubuntu1.2
nginx-light 1.18.0-0ubuntu1.2
Ubuntu 18.04 LTS:
nginx 1.14.0-0ubuntu1.9
nginx-common 1.14.0-0ubuntu1.9
nginx-core 1.14.0-0ubuntu1.9
nginx-extras 1.14.0-0ubuntu1.9
nginx-full 1.14.0-0ubuntu1.9
nginx-light 1.14.0-0ubuntu1.9
In general, a standard system update will make all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4967-1
CVE-2021-23017
Package Information:
https://launchpad.net/ubuntu/+source/nginx/1.18.0-6ubuntu8.2
https://launchpad.net/ubuntu/+source/nginx/1.18.0-6ubuntu2.2
https://launchpad.net/ubuntu/+source/nginx/1.18.0-0ubuntu1.2
https://launchpad.net/ubuntu/+source/nginx/1.14.0-0ubuntu1.9
Tuesday, May 25, 2021
Fedora Linux 32 End Of Life
Hello all,
As of the 25th of May 2021, Fedora Linux 32 has reached its end of
life for updates and support. No further updates, including security
updates, will be available for Fedora 32. All the updates that are
currently in testing won't get pushed to stable. Fedora 33 will
continue to receive updates until approximately one month after the
release of Fedora 35. The maintenance schedule of Fedora releases is
documented on the Fedora Project wiki [0]. The Fedora Project wiki
also contains instructions [1] on how to upgrade from a previous
release of Fedora to a version receiving updates.
Mohan Boddu.
[0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
[1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
As of the 25th of May 2021, Fedora Linux 32 has reached its end of
life for updates and support. No further updates, including security
updates, will be available for Fedora 32. All the updates that are
currently in testing won't get pushed to stable. Fedora 33 will
continue to receive updates until approximately one month after the
release of Fedora 35. The maintenance schedule of Fedora releases is
documented on the Fedora Project wiki [0]. The Fedora Project wiki
also contains instructions [1] on how to upgrade from a previous
release of Fedora to a version receiving updates.
Mohan Boddu.
[0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
[1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[USN-4966-2] libx11 vulnerability
==========================================================================
Ubuntu Security Notice USN-4966-2
May 25, 2021
libx11 vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 16.04 ESM
- Ubuntu 14.04 ESM
Summary:
libx11 could allow unintended access to services.
Software Description:
- libx11: X11 client-side library
Details:
USN-4966-1 fixed a vulnerability in libx11. This update provides
the corresponding update for Ubuntu 14.04 ESM and Ubuntu 16.04 ESM.
Original advisory details:
It was discovered that libx11 incorrectly validated certain parameter
lengths. A remote attacker could possibly use this issue to trick libx11
into emitting extra X protocol requests.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 16.04 ESM:
libx11-6 2:1.6.3-1ubuntu2.2+esm1
Ubuntu 14.04 ESM:
libx11-6 2:1.6.2-1ubuntu2.1+esm2
After a standard system update you need to reboot your computer to make
all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4966-2
https://ubuntu.com/security/notices/USN-4966-1
CVE-2021-31535
Ubuntu Security Notice USN-4966-2
May 25, 2021
libx11 vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 16.04 ESM
- Ubuntu 14.04 ESM
Summary:
libx11 could allow unintended access to services.
Software Description:
- libx11: X11 client-side library
Details:
USN-4966-1 fixed a vulnerability in libx11. This update provides
the corresponding update for Ubuntu 14.04 ESM and Ubuntu 16.04 ESM.
Original advisory details:
It was discovered that libx11 incorrectly validated certain parameter
lengths. A remote attacker could possibly use this issue to trick libx11
into emitting extra X protocol requests.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 16.04 ESM:
libx11-6 2:1.6.3-1ubuntu2.2+esm1
Ubuntu 14.04 ESM:
libx11-6 2:1.6.2-1ubuntu2.1+esm2
After a standard system update you need to reboot your computer to make
all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4966-2
https://ubuntu.com/security/notices/USN-4966-1
CVE-2021-31535
[USN-4965-2] Apport vulnerabilities
==========================================================================
Ubuntu Security Notice USN-4965-2
May 25, 2021
apport vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 16.04 ESM
- Ubuntu 14.04 ESM
Summary:
Several security issues were fixed in Apport.
Software Description:
- apport: automatically generate crash reports for debugging
Details:
USN-4965-1 fixed several vulnerabilities in Apport. This update provides
the corresponding update for Ubuntu 14.04 ESM and Ubuntu 16.04 ESM.
Original advisory details:
Maik Münch discovered that Apport incorrectly handled certain information
gathering operations. A local attacker could use these issues to read and
write arbitrary files as an administrator, and possibly escalate
privileges.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 16.04 ESM:
apport 2.20.1-0ubuntu2.30+esm1
python-apport 2.20.1-0ubuntu2.30+esm1
python3-apport 2.20.1-0ubuntu2.30+esm1
Ubuntu 14.04 ESM:
apport 2.14.1-0ubuntu3.29+esm7
python-apport 2.14.1-0ubuntu3.29+esm7
python3-apport 2.14.1-0ubuntu3.29+esm7
In general, a standard system update will make all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4965-2
https://ubuntu.com/security/notices/USN-4965-1
CVE-2021-32547, CVE-2021-32548, CVE-2021-32549, CVE-2021-32550,
CVE-2021-32551, CVE-2021-32552, CVE-2021-32553, CVE-2021-32554,
CVE-2021-32555, CVE-2021-32556, CVE-2021-32557
Ubuntu Security Notice USN-4965-2
May 25, 2021
apport vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 16.04 ESM
- Ubuntu 14.04 ESM
Summary:
Several security issues were fixed in Apport.
Software Description:
- apport: automatically generate crash reports for debugging
Details:
USN-4965-1 fixed several vulnerabilities in Apport. This update provides
the corresponding update for Ubuntu 14.04 ESM and Ubuntu 16.04 ESM.
Original advisory details:
Maik Münch discovered that Apport incorrectly handled certain information
gathering operations. A local attacker could use these issues to read and
write arbitrary files as an administrator, and possibly escalate
privileges.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 16.04 ESM:
apport 2.20.1-0ubuntu2.30+esm1
python-apport 2.20.1-0ubuntu2.30+esm1
python3-apport 2.20.1-0ubuntu2.30+esm1
Ubuntu 14.04 ESM:
apport 2.14.1-0ubuntu3.29+esm7
python-apport 2.14.1-0ubuntu3.29+esm7
python3-apport 2.14.1-0ubuntu3.29+esm7
In general, a standard system update will make all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4965-2
https://ubuntu.com/security/notices/USN-4965-1
CVE-2021-32547, CVE-2021-32548, CVE-2021-32549, CVE-2021-32550,
CVE-2021-32551, CVE-2021-32552, CVE-2021-32553, CVE-2021-32554,
CVE-2021-32555, CVE-2021-32556, CVE-2021-32557
[USN-4965-1] Apport vulnerabilities
==========================================================================
Ubuntu Security Notice USN-4965-1
May 25, 2021
apport vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 21.04
- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
Summary:
Several security issues were fixed in Apport.
Software Description:
- apport: automatically generate crash reports for debugging
Details:
Maik Münch discovered that Apport incorrectly handled certain information
gathering operations. A local attacker could use these issues to read and
write arbitrary files as an administrator, and possibly escalate
privileges.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 21.04:
apport 2.20.11-0ubuntu65.1
python3-apport 2.20.11-0ubuntu65.1
Ubuntu 20.10:
apport 2.20.11-0ubuntu50.7
python3-apport 2.20.11-0ubuntu50.7
Ubuntu 20.04 LTS:
apport 2.20.11-0ubuntu27.18
python3-apport 2.20.11-0ubuntu27.18
Ubuntu 18.04 LTS:
apport 2.20.9-0ubuntu7.24
python-apport 2.20.9-0ubuntu7.24
python3-apport 2.20.9-0ubuntu7.24
In general, a standard system update will make all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4965-1
CVE-2021-32547, CVE-2021-32548, CVE-2021-32549, CVE-2021-32550,
CVE-2021-32551, CVE-2021-32552, CVE-2021-32553, CVE-2021-32554,
CVE-2021-32555, CVE-2021-32556, CVE-2021-32557
Package Information:
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu65.1
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu50.7
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu27.18
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.24
Ubuntu Security Notice USN-4965-1
May 25, 2021
apport vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 21.04
- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
Summary:
Several security issues were fixed in Apport.
Software Description:
- apport: automatically generate crash reports for debugging
Details:
Maik Münch discovered that Apport incorrectly handled certain information
gathering operations. A local attacker could use these issues to read and
write arbitrary files as an administrator, and possibly escalate
privileges.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 21.04:
apport 2.20.11-0ubuntu65.1
python3-apport 2.20.11-0ubuntu65.1
Ubuntu 20.10:
apport 2.20.11-0ubuntu50.7
python3-apport 2.20.11-0ubuntu50.7
Ubuntu 20.04 LTS:
apport 2.20.11-0ubuntu27.18
python3-apport 2.20.11-0ubuntu27.18
Ubuntu 18.04 LTS:
apport 2.20.9-0ubuntu7.24
python-apport 2.20.9-0ubuntu7.24
python3-apport 2.20.9-0ubuntu7.24
In general, a standard system update will make all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4965-1
CVE-2021-32547, CVE-2021-32548, CVE-2021-32549, CVE-2021-32550,
CVE-2021-32551, CVE-2021-32552, CVE-2021-32553, CVE-2021-32554,
CVE-2021-32555, CVE-2021-32556, CVE-2021-32557
Package Information:
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu65.1
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu50.7
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu27.18
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.24
[USN-4966-1] libx11 vulnerability
==========================================================================
Ubuntu Security Notice USN-4966-1
May 25, 2021
libx11 vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 21.04
- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
Summary:
libx11 could allow unintended access to services.
Software Description:
- libx11: X11 client-side library
Details:
It was discovered that libx11 incorrectly validated certain parameter
lengths. A remote attacker could possibly use this issue to trick libx11
into emitting extra X protocol requests.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 21.04:
libx11-6 2:1.7.0-2ubuntu0.1
Ubuntu 20.10:
libx11-6 2:1.6.12-1ubuntu0.1
Ubuntu 20.04 LTS:
libx11-6 2:1.6.9-2ubuntu1.2
Ubuntu 18.04 LTS:
libx11-6 2:1.6.4-3ubuntu0.4
After a standard system update you need to reboot your computer to make
all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4966-1
CVE-2021-31535
Package Information:
https://launchpad.net/ubuntu/+source/libx11/2:1.7.0-2ubuntu0.1
https://launchpad.net/ubuntu/+source/libx11/2:1.6.12-1ubuntu0.1
https://launchpad.net/ubuntu/+source/libx11/2:1.6.9-2ubuntu1.2
https://launchpad.net/ubuntu/+source/libx11/2:1.6.4-3ubuntu0.4
Ubuntu Security Notice USN-4966-1
May 25, 2021
libx11 vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 21.04
- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
Summary:
libx11 could allow unintended access to services.
Software Description:
- libx11: X11 client-side library
Details:
It was discovered that libx11 incorrectly validated certain parameter
lengths. A remote attacker could possibly use this issue to trick libx11
into emitting extra X protocol requests.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 21.04:
libx11-6 2:1.7.0-2ubuntu0.1
Ubuntu 20.10:
libx11-6 2:1.6.12-1ubuntu0.1
Ubuntu 20.04 LTS:
libx11-6 2:1.6.9-2ubuntu1.2
Ubuntu 18.04 LTS:
libx11-6 2:1.6.4-3ubuntu0.4
After a standard system update you need to reboot your computer to make
all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4966-1
CVE-2021-31535
Package Information:
https://launchpad.net/ubuntu/+source/libx11/2:1.7.0-2ubuntu0.1
https://launchpad.net/ubuntu/+source/libx11/2:1.6.12-1ubuntu0.1
https://launchpad.net/ubuntu/+source/libx11/2:1.6.9-2ubuntu1.2
https://launchpad.net/ubuntu/+source/libx11/2:1.6.4-3ubuntu0.4
F35 Change: Make btrfs the default file system for Fedora Cloud (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/FedoraCloudBtrfsByDefault
== Summary ==
For cloud installs of Fedora, we want to provide advanced file system
features to users in a transparent fashion. Thus, we are changing the
file system for the Cloud Edition to Btrfs so we can leverage its
features and capabilities to improve the quality of experience for
Cloud users.
== Owners ==
* Name: [[User:Davdunc|David Duncan]], [[User:Chrismurphy|Chris
Murphy]], [[User:Josef|Josef Bacik]], [[User:Salimma|Michel Alexandre
Salim]], [[User:Dcavalca|Davide Cavalca]], [[User:Ngompa|Neal Gompa]],
[[User:Dustymabe|Dusty Mabe]], [[User:Malmond|Matthew Almond]]
* Email: davdunc@amazon.com, chrismurphy@fedoraproject.org,
josef@toxicpanda.com, michel@michel-slm.name, dcavalca@fb.com,
ngompa13@gmail.com, dusty@dustymabe.com, malmond@fb.com
* Products: Fedora Cloud Edition
* Responsible WGs: Fedora Cloud WG
== Detailed Description ==
Fedora Cloud Edition will switch to using Btrfs for its images. The
configuration for the Cloud Edition will match the setup used on the
desktop variants, as this has been very well-tested with production
deployments across multiple Fedora Linux releases now.
This includes the same subvolume layout that is used on the desktop
variants [[Changes/BtrfsByDefault|as introduced in Fedora Linux 33]],
as well as transparent Zstd compression
[[Changes/BtrfsTransparentCompression|as introduced in Fedora Linux
34]].
== Feedback ==
== Benefit to Fedora ==
The benefits are similar to
[[Changes/BtrfsByDefault#Benefit_to_Fedora|the ones for Fedora desktop
variants]]; however, there are specific benefits for Fedora Cloud:
* Adds support to Fedora Cloud for [[Changes/RPMCoW|the Change to
introduce support for Copy-on-Write enhancements to improve
performance to package management]]
* Adds the ability to logically separate contents of the volume
without dividing up the available space
** Transparent compression: significantly reduces write amplification
and improves effective I/O throughput
** Reflinks and snapshots improve efficiency for use cases like
containers (CRI-O, containerd, and Podman support both)
* Storage devices can be flaky, resulting in data corruption; Btrfs
can help mitigate this
** Everything is checksummed and verified on every read
** Corrupt data results in EIO (input/output error), instead of
resulting in application confusion, and isn't replicated into backups
and archives
* Improves system responsiveness under pressure
** Btrfs has been tested in production to have proper IO isolation
capability via cgroups2
** Completes the resource control picture: memory, cpu, IO isolation
* File system resize
** Online shrink and grow are cornerstones of the Btrfs design
* Complex storage setups are… complicated
** Simple and comprehensive command interface. One master command
** Simpler to boot, all code is in the kernel, no initramfs complexities
** Simple and efficient file system replication, including incremental
backups, with <code>btrfs send</code> and <code>btrfs receive</code>
== Scope ==
* Proposal owners:
** Submit PRs for Cloud Edition kickstarts to produce disk images using Btrfs.
* Release engineering: [https://pagure.io/releng/issue/10129 #10129]
* Policies and guidelines: N/A
* Trademark approval: N/A
== Upgrade/compatibility impact ==
Change will not affect upgrades.
== How To Test ==
Once the change lands in Rawhide, spin up the images in AWS, GCP, and
KVM/OpenStack to test to see systems boot and run.
== User Experience ==
* Mostly transparent.
* Space savings and extend hardware life, via compression.
* Utilities for used and free space are expected to behave the same.
No special commands are required.
* More detailed information can be revealed by <code>btrfs</code>
specific commands.
* <code>cp</code> command will create reflink copies
[https://src.fedoraproject.org/rpms/coreutils/c/5d08d14b/ by default.]
== Dependencies ==
None.
== Contingency Plan ==
* Contingency mechanism: Owner will revert changes back to the
previous ext4 configuration
* Contingency deadline: Beta freeze
* Blocks release? Yes
* Blocks product? Cloud
== Documentation ==
Strictly speaking, no extra documentation is required reading for users.
== Release Notes ==
The default file system on the cloud is now Btrfs, following the
desktop change in Fedora Linux 33. Fedora Server, IoT, and CoreOS are
still specifically excluded.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
== Summary ==
For cloud installs of Fedora, we want to provide advanced file system
features to users in a transparent fashion. Thus, we are changing the
file system for the Cloud Edition to Btrfs so we can leverage its
features and capabilities to improve the quality of experience for
Cloud users.
== Owners ==
* Name: [[User:Davdunc|David Duncan]], [[User:Chrismurphy|Chris
Murphy]], [[User:Josef|Josef Bacik]], [[User:Salimma|Michel Alexandre
Salim]], [[User:Dcavalca|Davide Cavalca]], [[User:Ngompa|Neal Gompa]],
[[User:Dustymabe|Dusty Mabe]], [[User:Malmond|Matthew Almond]]
* Email: davdunc@amazon.com, chrismurphy@fedoraproject.org,
josef@toxicpanda.com, michel@michel-slm.name, dcavalca@fb.com,
ngompa13@gmail.com, dusty@dustymabe.com, malmond@fb.com
* Products: Fedora Cloud Edition
* Responsible WGs: Fedora Cloud WG
== Detailed Description ==
Fedora Cloud Edition will switch to using Btrfs for its images. The
configuration for the Cloud Edition will match the setup used on the
desktop variants, as this has been very well-tested with production
deployments across multiple Fedora Linux releases now.
This includes the same subvolume layout that is used on the desktop
variants [[Changes/BtrfsByDefault|as introduced in Fedora Linux 33]],
as well as transparent Zstd compression
[[Changes/BtrfsTransparentCompression|as introduced in Fedora Linux
34]].
== Feedback ==
== Benefit to Fedora ==
The benefits are similar to
[[Changes/BtrfsByDefault#Benefit_to_Fedora|the ones for Fedora desktop
variants]]; however, there are specific benefits for Fedora Cloud:
* Adds support to Fedora Cloud for [[Changes/RPMCoW|the Change to
introduce support for Copy-on-Write enhancements to improve
performance to package management]]
* Adds the ability to logically separate contents of the volume
without dividing up the available space
** Transparent compression: significantly reduces write amplification
and improves effective I/O throughput
** Reflinks and snapshots improve efficiency for use cases like
containers (CRI-O, containerd, and Podman support both)
* Storage devices can be flaky, resulting in data corruption; Btrfs
can help mitigate this
** Everything is checksummed and verified on every read
** Corrupt data results in EIO (input/output error), instead of
resulting in application confusion, and isn't replicated into backups
and archives
* Improves system responsiveness under pressure
** Btrfs has been tested in production to have proper IO isolation
capability via cgroups2
** Completes the resource control picture: memory, cpu, IO isolation
* File system resize
** Online shrink and grow are cornerstones of the Btrfs design
* Complex storage setups are… complicated
** Simple and comprehensive command interface. One master command
** Simpler to boot, all code is in the kernel, no initramfs complexities
** Simple and efficient file system replication, including incremental
backups, with <code>btrfs send</code> and <code>btrfs receive</code>
== Scope ==
* Proposal owners:
** Submit PRs for Cloud Edition kickstarts to produce disk images using Btrfs.
* Release engineering: [https://pagure.io/releng/issue/10129 #10129]
* Policies and guidelines: N/A
* Trademark approval: N/A
== Upgrade/compatibility impact ==
Change will not affect upgrades.
== How To Test ==
Once the change lands in Rawhide, spin up the images in AWS, GCP, and
KVM/OpenStack to test to see systems boot and run.
== User Experience ==
* Mostly transparent.
* Space savings and extend hardware life, via compression.
* Utilities for used and free space are expected to behave the same.
No special commands are required.
* More detailed information can be revealed by <code>btrfs</code>
specific commands.
* <code>cp</code> command will create reflink copies
[https://src.fedoraproject.org/rpms/coreutils/c/5d08d14b/ by default.]
== Dependencies ==
None.
== Contingency Plan ==
* Contingency mechanism: Owner will revert changes back to the
previous ext4 configuration
* Contingency deadline: Beta freeze
* Blocks release? Yes
* Blocks product? Cloud
== Documentation ==
Strictly speaking, no extra documentation is required reading for users.
== Release Notes ==
The default file system on the cloud is now Btrfs, following the
desktop change in Fedora Linux 33. Fedora Server, IoT, and CoreOS are
still specifically excluded.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[USN-4964-1] Exiv2 vulnerabilities
==========================================================================
Ubuntu Security Notice USN-4964-1
May 25, 2021
exiv2 vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 21.04
- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
- Ubuntu 16.04 ESM
Summary:
Several security issues were fixed in Exiv2.
Software Description:
- exiv2: EXIF/IPTC/XMP metadata manipulation tool
Details:
It was discovered that Exiv2 incorrectly handled certain files.
An attacker could possibly use this issue to cause a denial of service.
This issue only affected Ubuntu 20.04 LTS, Ubuntu 20.10 and Ubuntu 21.04.
(CVE-2021-29463)
It was discovered that Exiv2 incorrectly handled certain files.
An attacker could possibly use this issue to execute arbitrary code.
This issue only affected Ubuntu 20.04 LTS, Ubuntu 20.10 and Ubuntu 21.04.
(CVE-2021-29464)
It was discovered that Exiv2 incorrectly handled certain files.
An attacker could possibly use this issue to cause a denial of service.
(CVE-2021-29473, CVE-2021-32617)
It was discovered that Exiv2 incorrectly handled certain files.
An attacker could possibly use this issue to expose sensitive information.
This issue only affected Ubuntu 20.04 LTS, Ubuntu 20.10 and Ubuntu 21.04.
(CVE-2021-29623)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 21.04:
exiv2 0.27.3-3ubuntu1.3
libexiv2-27 0.27.3-3ubuntu1.3
Ubuntu 20.10:
exiv2 0.27.3-3ubuntu0.4
libexiv2-27 0.27.3-3ubuntu0.4
Ubuntu 20.04 LTS:
exiv2 0.27.2-8ubuntu2.4
libexiv2-27 0.27.2-8ubuntu2.4
Ubuntu 18.04 LTS:
exiv2 0.25-3.1ubuntu0.18.04.9
libexiv2-14 0.25-3.1ubuntu0.18.04.9
Ubuntu 16.04 ESM:
exiv2 0.25-2.1ubuntu16.04.7+esm2
libexiv2-14 0.25-2.1ubuntu16.04.7+esm2
In general, a standard system update will make all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4964-1
CVE-2021-29463, CVE-2021-29464, CVE-2021-29473, CVE-2021-29623,
CVE-2021-32617
Package Information:
https://launchpad.net/ubuntu/+source/exiv2/0.27.3-3ubuntu1.3
https://launchpad.net/ubuntu/+source/exiv2/0.27.3-3ubuntu0.4
https://launchpad.net/ubuntu/+source/exiv2/0.27.2-8ubuntu2.4
https://launchpad.net/ubuntu/+source/exiv2/0.25-3.1ubuntu0.18.04.9
Ubuntu Security Notice USN-4964-1
May 25, 2021
exiv2 vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 21.04
- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS
- Ubuntu 16.04 ESM
Summary:
Several security issues were fixed in Exiv2.
Software Description:
- exiv2: EXIF/IPTC/XMP metadata manipulation tool
Details:
It was discovered that Exiv2 incorrectly handled certain files.
An attacker could possibly use this issue to cause a denial of service.
This issue only affected Ubuntu 20.04 LTS, Ubuntu 20.10 and Ubuntu 21.04.
(CVE-2021-29463)
It was discovered that Exiv2 incorrectly handled certain files.
An attacker could possibly use this issue to execute arbitrary code.
This issue only affected Ubuntu 20.04 LTS, Ubuntu 20.10 and Ubuntu 21.04.
(CVE-2021-29464)
It was discovered that Exiv2 incorrectly handled certain files.
An attacker could possibly use this issue to cause a denial of service.
(CVE-2021-29473, CVE-2021-32617)
It was discovered that Exiv2 incorrectly handled certain files.
An attacker could possibly use this issue to expose sensitive information.
This issue only affected Ubuntu 20.04 LTS, Ubuntu 20.10 and Ubuntu 21.04.
(CVE-2021-29623)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 21.04:
exiv2 0.27.3-3ubuntu1.3
libexiv2-27 0.27.3-3ubuntu1.3
Ubuntu 20.10:
exiv2 0.27.3-3ubuntu0.4
libexiv2-27 0.27.3-3ubuntu0.4
Ubuntu 20.04 LTS:
exiv2 0.27.2-8ubuntu2.4
libexiv2-27 0.27.2-8ubuntu2.4
Ubuntu 18.04 LTS:
exiv2 0.25-3.1ubuntu0.18.04.9
libexiv2-14 0.25-3.1ubuntu0.18.04.9
Ubuntu 16.04 ESM:
exiv2 0.25-2.1ubuntu16.04.7+esm2
libexiv2-14 0.25-2.1ubuntu16.04.7+esm2
In general, a standard system update will make all the necessary changes.
References:
https://ubuntu.com/security/notices/USN-4964-1
CVE-2021-29463, CVE-2021-29464, CVE-2021-29473, CVE-2021-29623,
CVE-2021-32617
Package Information:
https://launchpad.net/ubuntu/+source/exiv2/0.27.3-3ubuntu1.3
https://launchpad.net/ubuntu/+source/exiv2/0.27.3-3ubuntu0.4
https://launchpad.net/ubuntu/+source/exiv2/0.27.2-8ubuntu2.4
https://launchpad.net/ubuntu/+source/exiv2/0.25-3.1ubuntu0.18.04.9
Monday, May 24, 2021
[arch-announce] Move of official IRC channels to libera.chat
As some of you may have read over the past days, there has been an ownership dispute over the [freenode.net](https://freenode.net) network. The IRC network has been used by Arch Linux and many other projects over the past decades as a platform for discussion and support.
The dispute led to the exodus of most former freenode staff from the network and the founding of a new network: [libera.chat](https://libera.chat)
Starting today, Arch Linux and its sister projects [Arch Linux ARM](https://archlinuxarm.org) and [Arch Linux 32](https://archlinux32.org) will begin migrating the official IRC channels from freenode.net to libera.chat. Please bear with us as this can take some time to be fully settled in.
We thank the freenode community for the many years of great service and collaboration.
URL: https://archlinux.org/news/move-of-official-irc-channels-to-liberachat/
_______________________________________________
arch-announce mailing list
arch-announce@lists.archlinux.org
https://lists.archlinux.org/listinfo/arch-announce
The dispute led to the exodus of most former freenode staff from the network and the founding of a new network: [libera.chat](https://libera.chat)
Starting today, Arch Linux and its sister projects [Arch Linux ARM](https://archlinuxarm.org) and [Arch Linux 32](https://archlinux32.org) will begin migrating the official IRC channels from freenode.net to libera.chat. Please bear with us as this can take some time to be fully settled in.
We thank the freenode community for the many years of great service and collaboration.
URL: https://archlinux.org/news/move-of-official-irc-channels-to-liberachat/
_______________________________________________
arch-announce mailing list
arch-announce@lists.archlinux.org
https://lists.archlinux.org/listinfo/arch-announce
Subscribe to:
Posts (Atom)