January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1012389] New: xfce4-terminal immediately becomes zombie
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1012389 Bug ID: 1012389 Summary: xfce4-terminal immediately becomes zombie Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: christoph.wickert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading to Leap 42.2, xfce4-terminal becomes a zombie immediately after launched. Reproducibility: Always Hot to reproduce: 1. Launch xfce4-terminal 2. Run 'ps aux | grep Z' in that terminal. Result: You will see that the very xfce4-terminal you are using is a zombie. 'kill' or 'kill -9' don't work, so we use pstree to find the zombie's parent. It's another xfce4-terminal instance which responds to signals fine. Expected result: xfce4-terminal should not be a zombie. Not sure if there should be two instances of it. Affected packages xfce4-terminal-0.6.3-4.16.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 926323] New: VUL-1: CVE-2015-1821,CVE-2015-1822, 2015-1853: chrony: multiple vulnerabilities
by bugzilla_noreply＠novell.com 30 Oct '18

30 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=926323 Bug ID: 926323 Summary: VUL-1: CVE-2015-1821,CVE-2015-1822, 2015-1853: chrony: multiple vulnerabilities Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: opensuse-communityscreening(a)forge.provo.novell.com Reporter: astieger(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: david.bahi(a)emc.com, mkudlvasr(a)novell.com, mrueckert(a)suse.com Found By: Security Response Team Blocker: --- Reported against network:time chrony, not in openSUSE or SLE. Does not have a designated maintainer, CC project maintainers and recent updaters. CVE-2015-1821 chrony: Heap out of bound write in address filter =============================================================== https://bugzilla.redhat.com/show_bug.cgi?id=1209632 Miroslav Lichvar of Red Hat reports: When NTP or cmdmon access is configured (from chrony.conf or over authenticated cmdmon) with a subnet size that is not divisible by 4 and address that has nonzero bits in the 4-bit subnet remainder (e.g. f0::/3), the TableNode array index is calculated incorrectly and it may write past the array. CVE-2015-1822 chrony: uninitialized pointer in cmdmon reply slots ================================================================= https://bugzilla.redhat.com/show_bug.cgi?id=1209632 Miroslav Lichvar of Red Hat reports: The last pointer in the list of allocated reply slots that are used to save authenticated cmdmon replies is not initialized. This one was actually found couple months ago and it's already fixed in git, but only recently I realized it could have security implications. An authenticated attacker can allocate and deallocate memory with other commands (e.g. allow/deny) and can force allocation of new reply slots by making new requests and not acknowledging previous replies, and then let chronyd write a reply to an invalid memory. CVE-2015-1853 chrony: authentication doesn't protect symmetric associations against DoS attacks =============================================================================================== https://bugzilla.redhat.com/show_bug.cgi?id=1209572 Miroslav Lichvar of Red Hat reports: An attacker knowing that NTP hosts A and B are peering with each other (symmetric association) can send a packet to host A with source address of B which will set the NTP state variables on A to the values sent by the attacker. Host A will then send on its next poll to B a packet with originate timestamp that doesn't match the transmit timestamp of B and the packet will be dropped. If the attacker does this periodically for both hosts, they won't be able to synchronize to each other. This is a known denial-of-service attack, described at [1]. According to the document the NTP authentication is supposed to protect symmetric associations against this attack, but that doesn't seem to be the case. The state variables are updated even when authentication fails and the peers are sending packets with originate timestamps that don't match the transmit timestamps on the receiving side. This seems to be a very old problem, it's in the oldest ntp version I could find (xntp3.3wy). It's also in the NTPv3 (RFC 1305) and NTPv4 (RFC 5905) specifications, so other NTP implementations with support for symmetric associations and authentication may be vulnerable too. For authentication using symmetric keys it should be sufficient to move the code updating the state variables after the MAC is validated (TEST5). For autokey that's not enough, it seems the attacker can still reset the protocol with crypto-NAK or CRYPTO_ASSOC messages and possibly other ways. I'm not sure if this can be fixed for autokey in general. [1] https://www.eecis.udel.edu/~mills/onwire.html -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 872984] New: /etc/apparmor.d/usr.lib.apache2.mpm-prefork.apache2 too broad
by bugzilla_noreply＠novell.com 30 Oct '18

30 Oct '18

https://bugzilla.novell.com/show_bug.cgi?id=872984 https://bugzilla.novell.com/show_bug.cgi?id=872984#c0 Summary: /etc/apparmor.d/usr.lib.apache2.mpm-prefork.apache2 too broad Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: suse-beta(a)cboltz.de ReportedBy: meissner(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- /etc/apparmor.d/usr.lib.apache2.mpm-prefork.apache2 does / rw, /** mrwlkix, so basically ... every process can do everything. Correct me if I am wrong, but this profile is then not necessary. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 964185] New: kdeinit5 crashes
by bugzilla_noreply＠novell.com 28 Oct '18

28 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=964185 Bug ID: 964185 Summary: kdeinit5 crashes Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ludwig(a)sics.se QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kdeinit5 crashes unexpectedly. Sometimes this happens while my screensaver is on, which disables the (password protected) screensaver, which is why I consider this to be a Major security issue. I can get the following information out of the crash report: Executable: kdeinit5 PID: 1485 Signal: Segmentation fault (11) Time: 2016-01-29 14:40:51 Thread 1 (Thread 0x7f81a4708780 (LWP 1485)): [KCrash Handler] #6 0x00007f819172d9cf in QXcbWindow::handleClientMessageEvent(xcb_client_message_event_t const*) () at /usr/lib64/libQt5XcbQpa.so.5 #7 0x00007f819171837b in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /usr/lib64/libQt5XcbQpa.so.5 #8 0x00007f819171a01b in QXcbConnection::processXcbEvents() () at /usr/lib64/libQt5XcbQpa.so.5 #9 0x00007f81a3020ac6 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x00007f81a166fe7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #11 0x00007f81a1674cc8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #12 0x00007f81a2fefe95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x00007f81a2ff2057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #14 0x00007f81a30478f3 in () at /usr/lib64/libQt5Core.so.5 #15 0x00007f819f7f3c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #16 0x00007f819f7f3ed8 in () at /usr/lib64/libglib-2.0.so.0 #17 0x00007f819f7f3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #18 0x00007f81a3046d6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #19 0x00007f81a2fedd53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #20 0x00007f81a2ff58f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #21 0x00007f8191bd05b4 in kdemain () at /usr/lib64/libkdeinit5_kded5.so #22 0x0000000000408cc3 in () #23 0x0000000000405d46 in main () -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1012847] New: ooRexx shouldn't ship any preset file
by bugzilla_noreply＠novell.com 27 Oct '18

27 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=1012847 Bug ID: 1012847 Summary: ooRexx shouldn't ship any preset file Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, Preset files are supposed to be shipped by the branding package so the secteam can review carefully which packages are enabled by default on a given distro. Could anybody move the content of the preset file to the branding package ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 948729] New: YaST: System Log
by bugzilla_noreply＠novell.com 26 Oct '18

26 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=948729 Bug ID: 948729 Summary: YaST: System Log Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: otuominen(a)novell.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- There is nomore log in: /var/log/messages So can this tool put to track journalctl log? /var/log/boot.log is still valid. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 803057] New: PostgreSQL 9.2.3, 9.1.8, 9.0.12, 8.4.16 and 8.3.23 released
by bugzilla_noreply＠novell.com 23 Oct '18

23 Oct '18

https://bugzilla.novell.com/show_bug.cgi?id=803057 https://bugzilla.novell.com/show_bug.cgi?id=803057#c0 Summary: PostgreSQL 9.2.3, 9.1.8, 9.0.12, 8.4.16 and 8.3.23 released Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: lijewski.stefan(a)zabka.pl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 >From postgresql.org: The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) vulnerability. All users should update their PostgreSQL installations as soon as possible. The security issue fixed in this release, CVE-2013-0255, allows a previously authenticated user to crash the server by calling an internal function with invalid arguments. This issue was discovered by independent security researcher Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for their efforts in making PostgreSQL more secure. Today's update also fixes a performance regression which caused a decrease in throughput when using dynamic queries in stored procedures in version 9.2. Applications which use PL/pgSQL's EXECUTE are strongly affected by this regression and should be updated. Additionally, we have fixed intermittent crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with replication. Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 933032] New: KDE Breeze Dark theme in new Plasma workspace no longer renders correctly
by bugzilla_noreply＠novell.com 20 Oct '18

20 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=933032 Bug ID: 933032 Summary: KDE Breeze Dark theme in new Plasma workspace no longer renders correctly Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace Assignee: kde-maintainers(a)suse.de Reporter: jrhodes(a)redpointsoftware.com.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36 Build Identifier: After performing "zypper up" today, the Breeze Dark theme in the Plasma workspace no longer renders correctly, as per the attached screenshot. Reproducible: Always Steps to Reproduce: 1. Select the "Breeze Dark" theme on KDE 5 / Plasma. Actual Results: The panel at the bottom of the screen still has a white background. Expected Results: The panel at the bottom should be themed correctly (have a dark background). -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 820566] New: wireshark security updates to 1.8.7 and 1.6.15
by bugzilla_noreply＠novell.com 19 Oct '18

19 Oct '18

https://bugzilla.novell.com/show_bug.cgi?id=820566 https://bugzilla.novell.com/show_bug.cgi?id=820566#c0 Summary: wireshark security updates to 1.8.7 and 1.6.15 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: Andreas.Stieger(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0 https://www.wireshark.org/docs/relnotes/wireshark-1.8.7.html wnpa-sec-2013-23 CVE-2013-2486 CVE-2013-2487 The RELOAD dissector could go into an infinite loop. wnpa-sec-2013-24 The GTPv2 dissector could crash. wnpa-sec-2013-25 The ASN.1 BER dissector could crash. wnpa-sec-2013-26 The PPP CCP dissector could crash. wnpa-sec-2013-27 The DCP ETSI dissector could crash. wnpa-sec-2013-28 The MPEG DSM-CC dissector could crash. wnpa-sec-2013-29 The Websocket dissector could crash. wnpa-sec-2013-30 The MySQL dissector could go into an infinite loop. wnpa-sec-2013-31 The ETCH dissector could go into a large loop. https://www.wireshark.org/docs/relnotes/wireshark-1.6.15.html 1.6.15 wnpa-sec-2013-25 The ASN.1 BER dissector could crash Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 15

[Bug 974661] New: wicked resets host name after wickedd restart
by bugzilla_noreply＠novell.com 19 Oct '18

19 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=974661 Bug ID: 974661 Summary: wicked resets host name after wickedd restart Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: All OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: johannes.grassler(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Build Identifier: We recently had an issue with one of our Jenkins jobs failing due to the machine's host name reverting to 'linux' after wickedd is restarted (see [0] for details). The machine in question had its hostname set to 'cleanvm.openstacklocal' by cloud-init. At a later point our QA script restarted wickedd and wickedd reverted the hostname to 'linux'. The problem appears to be caused by /etc/wicked/extensions/hostname. When we disabled that script by an `exit 0` at the top wicked no longer reset the host name. Adding some debugging output narrowed the problem down to the `install` operation in /etc/wicked/extensions/hostname. Specifically, wickedd set the hostname to `linux` (found in the hostname section of /var/lib/wicked/lease-eth0-dhcp-ipv4.xml but just putting an arbitrary value in there did not reset the host name to that arbitrary value, so probably the source of truth is somewhere else). [0] https://github.com/SUSE-Cloud/automation/pull/945 Reproducible: Always Steps to Reproduce: 1. Boot a VM with this image: http://download.opensuse.org/repositories/openSUSE:/Leap:/42.1:/Images/imag… 2. Set the machine's host name to an arbitrary value (either manually using hostnamectl or through cloud-init) 3. Issue a `systemctl restart wickedd`. After this the machine's run-time host name will change to `linux`. Actual Results: The machine's host name changed to `linux`. Expected Results: The host name should have remained the one originally set by cloud-init and found in /etc/hostname and /proc/sys/kernel/hostname (cleanvm.openstacklocal in the case at hand). -- You are receiving this mail because: You are on the CC list for the bug.

1 2