Potential pre-authentication buffer overflow due to integer overflow in exec/totemcrypto.c:authenticate_nss_2_3() function can lead to denial of service or potentially to remote code execution. corosync before version 2.4.4 is vulnerable. Gentoo Security Scout Florian Schuhmacher
CVE-2018-1084 Detail Current Description corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c.
@maintainers, please create an appropriate ebuild, and call for stabilisation when ready.
ping
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e50ae9c2a0231556f783652e6951e49222744bd0 commit e50ae9c2a0231556f783652e6951e49222744bd0 Author: Timo Rothenpieler <btbn@btbn.de> AuthorDate: 2020-07-24 19:34:00 +0000 Commit: Alexys Jacob <ultrabug@gentoo.org> CommitDate: 2020-10-21 12:58:09 +0000 sys-cluster/corosync: bump for 3.0.4 Bug: https://bugs.gentoo.org/658354 Signed-off-by: Timo Rothenpieler <btbn@btbn.de> Signed-off-by: Alexys Jacob <ultrabug@gentoo.org> sys-cluster/corosync/Manifest | 1 + sys-cluster/corosync/corosync-3.0.4.ebuild | 69 ++++++++++++++++++++++++++++++ 2 files changed, 70 insertions(+)
Please stabilize when ready.
Sanity check failed: > sys-cluster/corosync-3.0.4 > depend amd64 stable profile default/linux/amd64/17.0 (61 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:= > depend amd64 dev profile default/linux/amd64/17.0/no-multilib/prefix/kernel-3.2+ (4 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:= > rdepend amd64 stable profile default/linux/amd64/17.0 (61 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:= > rdepend amd64 dev profile default/linux/amd64/17.0/no-multilib/prefix/kernel-3.2+ (4 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:=
Sanity check failed: > sys-cluster/corosync-3.0.4 > depend amd64 dev profile default/linux/amd64/17.0/no-multilib/prefix/kernel-3.2+ (4 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:= > depend amd64 stable profile default/linux/amd64/17.1 (47 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:= > rdepend amd64 dev profile default/linux/amd64/17.0/no-multilib/prefix/kernel-3.2+ (4 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:= > rdepend amd64 stable profile default/linux/amd64/17.1 (47 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:=
Sanity check failed: > sys-cluster/corosync-3.0.4 > depend amd64 dev profile default/linux/amd64/17.0/no-multilib/prefix/kernel-3.2+ (5 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:= > depend amd64 stable profile default/linux/amd64/17.1 (47 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:= > rdepend amd64 dev profile default/linux/amd64/17.0/no-multilib/prefix/kernel-3.2+ (5 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:= > rdepend amd64 stable profile default/linux/amd64/17.1 (47 total) > >=sys-cluster/libqb-2.0.0:= > sys-cluster/kronosnet:=
Unable to check for sanity: > no match for package: sys-cluster/corosync-3.0.4
Resetting sanity check; keywords are not fully specified and arches are not CC-ed.
Sanity check failed: > sys-cluster/corosync-3.1.0 > depend ppc64 stable profile default/linux/powerpc/ppc64/17.0/64bit-userland (9 total) > app-admin/augeas > depend ppc64 dev profile default/linux/ppc64le/17.0/desktop/plasma (2 total) > app-admin/augeas > rdepend ppc64 stable profile default/linux/powerpc/ppc64/17.0/64bit-userland (9 total) > app-admin/augeas > rdepend ppc64 dev profile default/linux/ppc64le/17.0/desktop/plasma (2 total) > app-admin/augeas
Sanity check failed: > app-admin/augeas-1.12.0 > depend ppc64 stable profile default/linux/powerpc/ppc64/17.0/64bit-userland (9 total) > >=app-doc/NaturalDocs-1.40 > depend ppc64 dev profile default/linux/ppc64le/17.0/desktop/plasma (2 total) > >=app-doc/NaturalDocs-1.40
Unable to check for sanity: > disallowed package spec (only = allowed): app-doc/NaturalDocs
All sanity-check issues have been resolved
ppc64 done
amd64 done
x86 done
ppc done all arches done
Please cleanup.
New GLSA request filed.
This issue was resolved and addressed in GLSA 202107-01 at https://security.gentoo.org/glsa/202107-01 by GLSA coordinator John Helmert III (ajak).