December 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1179930] New: VUL-0: CVE-2020-26418: wireshark: Kafka dissector memory leak (wnpa-sec-2020-16)
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179930 Bug ID: 1179930 Summary: VUL-0: CVE-2020-26418: wireshark: Kafka dissector memory leak (wnpa-sec-2020-16) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: rfrohl(a)suse.com Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- Kafka dissector memory leak fixed in 3.2.9, 3.4.1 References: https://www.wireshark.org/security/wnpa-sec-2020-16 https://gitlab.com/wireshark/wireshark/-/issues/16739 https://www.wireshark.org/lists/wireshark-announce/202012/msg00000.html https://www.wireshark.org/lists/wireshark-announce/202012/msg00001.html -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175496] yast-security: obsolete SYSTOHC
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1175496 https://bugzilla.suse.com/show_bug.cgi?id=1175496#c3 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lnussel(a)suse.com) | --- Comment #3 from Ludwig Nussel <lnussel(a)suse.com> --- From a quick glance neither chrony nor systemd seem to use DEFAULT_TIMEZONE. I assume it was always something yast internal. The system's timezone is defined via the link /etc/localtime. So the setting and the file as a whole is probably obsolete. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179299] With kernel-default-5.3.18-lp152.50.1 i get stuck IO
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179299 https://bugzilla.suse.com/show_bug.cgi?id=1179299#c5 --- Comment #5 from Glei <flo(a)redflo.de> --- In the mean time i swapped a suspicious (disk /dev/sdg). Yesterday i switched from kernel 5.3.18-lp152.33 to the most recent, and this morning i got a IO lockup again. I attached kernel messages, but i think, they are not complete, because writes did not finish. After 1 hour waiting for "sync" to complete, i had to hard reset, and switched back to the old kernel. Nightly i have a lot of IO: mdcheck continues to run and backup routines read from some filesystems and write to the backup volume. The backup volume has been moved (with pvmove) from /dev/md3 to /dev/md1 after spwapping /dev/sdg. During IO lockup i also saw md mismatch sector in range errors. I guess this is due to IO lockup, but i will try to re-check /dev/md3 which usually takes 1-2 days. The messages are grepped to show "kernel:" only messages. If you need more, i can provide, but maybe not drop then here public. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179928] New: VUL-0: CVE-2020-26271:tensorflow, tensorflow2: Loading a saved model can result in accessing uninitialized memory in the MakeEdge function
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179928 Bug ID: 1179928 Summary: VUL-0: CVE-2020-26271:tensorflow, tensorflow2: Loading a saved model can result in accessing uninitialized memory in the MakeEdge function Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/273152/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: cgoll(a)suse.com Reporter: jsegitz(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2020-26271 In affected versions of TensorFlow under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge function creates an edge between one output tensor of the src node (given by output_index) and the input slot of the dst node (given by input_index). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType values and comparing these for equality. However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays. In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0. Affects Leap 15.2 and Factory in both packages. Also tensorflow2 is in a lower version in Factory than in Leap, that shouldn't be the case References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-26271 https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q263-fvxm… http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26271 https://github.com/tensorflow/tensorflow/commit/0cc38aaa4064fd9e79101994ce9… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179299] With kernel-default-5.3.18-lp152.50.1 i get stuck IO
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179299 https://bugzilla.suse.com/show_bug.cgi?id=1179299#c4 Glei <flo(a)redflo.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(flo(a)redflo.de) | --- Comment #4 from Glei <flo(a)redflo.de> --- Created attachment 844385 --> https://bugzilla.suse.com/attachment.cgi?id=844385&action=edit Kernel messages -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179299] With kernel-default-5.3.18-lp152.50.1 i get stuck IO
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179299 https://bugzilla.suse.com/show_bug.cgi?id=1179299#c3 --- Comment #3 from Glei <flo(a)redflo.de> --- Created attachment 844384 --> https://bugzilla.suse.com/attachment.cgi?id=844384&action=edit Output from lsblk and other commands -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179923] Package apache-rpm-macros is broken!
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179923 https://bugzilla.suse.com/show_bug.cgi?id=1179923#c1 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Petr Gajdos <pgajdos(a)suse.com> --- Thanks, this has been already fixed in devel project and it is on way to factory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175496] yast-security: obsolete SYSTOHC
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1175496 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast-internal(a)suse.de |schubi(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175496] yast-security: obsolete SYSTOHC
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1175496 https://bugzilla.suse.com/show_bug.cgi?id=1175496#c2 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel(a)suse.com, | |schubi(a)suse.com Flags| |needinfo?(lnussel(a)suse.com) --- Comment #2 from Stefan Schubert <schubi(a)suse.com> --- Hm, Rudis patch is talking about removing/not_using /etc/sysconfig/clock at all. Or does it mean that aaa_base is not handling this file anymore but it is still valid and used by other packages ? For example in our country package: country/timezone/src/modules/Timezone.rb: SCR.Write(path(".sysconfig.clock.DEFAULT_TIMEZONE"), @default_timezone) Anyway I will remove the handling of SYSTOHC at first. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179923] New: Package apache-rpm-macros is broken!
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179923 Bug ID: 1179923 Summary: Package apache-rpm-macros is broken! Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Apache Assignee: bnc-team-apache(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently the build of info2hrml does break with the message: [ 45s] info2html-2.0-0.noarch.rpm: directories not owned by a package: [ 45s] - /usr/cgi-bin [ 45s] - /usr/htdocs now as the build of info2hrml uses the macro %{apache_serverroot} defined in /usr/lib/rpm/macros.d/macros.apache of package apache-rpm-macros this points out that this can not be correct as in the spec file of apache-rpm-macros there is the line %define ap_serverroot %(%{ap_apxs} -q PREFIX) and if I run apxs -q PREFIX it reports /usr but the package apache2.spec shows %define datadir /srv/www cat > config.layout <<-EOF # SUSE Layout <Layout SUSE> prefix: %{datadir} exec_prefix: %{_prefix} bindir: %{_bindir} sbindir: %{_sbindir} libdir: %{_libdir} libexecdir: %{libexecdir} mandir: %{_mandir} sysconfdir: %{sysconfdir} datadir: %{datadir} installbuilddir: %{installbuilddir} errordir: %{errordir} iconsdir: %{iconsdir} htdocsdir: %{htdocsdir} manualdir: %{manualdir} cgidir: %{cgidir} includedir: %{includedir} localstatedir: %{localstatedir} runtimedir: %{runtimedir} logfiledir: %{logfiledir} proxycachedir: %{proxycachedir} </Layout> Please correct this or define a macro for directory for cgi binaries as well as a directory for htdocs files as well -- You are receiving this mail because: You are on the CC list for the bug.

1 1