April 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1095670] New: Problem with suid pgms on Leap-15.0
by bugzilla_noreply＠novell.com 24 Nov '21

24 Nov '21

http://bugzilla.suse.com/show_bug.cgi?id=1095670 Bug ID: 1095670 Summary: Problem with suid pgms on Leap-15.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmarkh(a)cfl.rr.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am upgrading an older SuSE-13.2 box to Leap. I have done a fresh Leap-15.0 install and ported over the source code that we ran on the 13.2 box. It builds fine but I am having an issue. The program is/has to be an suid pgm. It also uses fork/execvpe/wait to execute some external scripts. And that is where my problem lies. The user is a member of several groups but these group memberships seem to disappear when these external scripts are executed. For instance the user is a member of the cdrom group so he can eject and work with a DVD. I have created a simple example script and source for a pgm that execvpe's that script which shows my problem. test.sh script: #!/bin/sh whoami id test.c pgm source: #define _GNU_SOURCE #include <unistd.h> #include <stdio.h> #include <stdlib.h> #include <string.h> int main() { char *path = getenv("PATH"); char pathenv[strlen(path) + sizeof("PATH=")]; sprintf(pathenv, "PATH=%s", path); char *envp[] = {pathenv, NULL}; char *tests[] = {"./test.sh", NULL}; execvpe(tests[0], tests, envp); } #cc test.c #/a.out markh uid=5076(markh) gid=100(users) groups=100(users),19(floppy),200(lcrs),484(tape),485(lp),488(disk),489(dialout),490(cdrom) Then as root: #chown root ./a.out #chgrp root ./a.out #chmod +s ./a.out Then as user #./a.out markh uid=5076(markh) gid=100(users) groups=100(users) Once the pgm is owned by root and suid, I lose all my group memberships for some unknown reason. It is not proper to me. This all works fine on 13.2 but does not on Leap 15 or Leap 42.3. Is there some security setting somewhere that broke this? -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1139098] New: VUL-0: CVE-2018-18838: netdata: Log Injection
by bugzilla_noreply＠novell.com 24 Nov '21

24 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1139098 Bug ID: 1139098 Summary: VUL-0: CVE-2018-18838: netdata: Log Injection Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://smash.suse.de/issue/235366/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2018-18838 An issue was discovered in Netdata 1.10.0. Log Injection (or Log Forgery) exists via a %0a sequence in the url parameter to api/v1/registry. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-18838 http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-18838.html http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18838 https://www.red4sec.com/cve/netdata_log_injection.txt https://github.com/netdata/netdata/commit/92327c9ec211bd1616315abcb255861b1… https://github.com/netdata/netdata/pull/4521 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1139095] New: VUL-0: CVE-2018-18837: netdata: HTTP Header Injection
by bugzilla_noreply＠novell.com 24 Nov '21

24 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1139095 Bug ID: 1139095 Summary: VUL-0: CVE-2018-18837: netdata: HTTP Header Injection Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://smash.suse.de/issue/235365/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2018-18837 An issue was discovered in Netdata 1.10.0. HTTP Header Injection exists via the api/v1/data filename parameter because of web_client_api_request_v1_data in web/api/web_api_v1.c. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-18837 http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-18837.html http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18837 https://www.red4sec.com/cve/netdata_header_injection.txt https://github.com/netdata/netdata/pull/4521 https://github.com/netdata/netdata/commit/92327c9ec211bd1616315abcb255861b1… https://github.com/netdata/netdata/blob/798c141c49ee85bddc8f48f25d2cb593ec9… -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1139094] New: VUL-0: CVE-2018-18836: netdata: JSON injection
by bugzilla_noreply＠novell.com 24 Nov '21

24 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1139094 Bug ID: 1139094 Summary: VUL-0: CVE-2018-18836: netdata: JSON injection Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://smash.suse.de/issue/235364/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2018-18836 An issue was discovered in Netdata 1.10.0. JSON injection exists via the api/v1/data tqx parameter because of web_client_api_request_v1_data in web/api/web_api_v1.c. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-18836 http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-18836.html http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18836 https://github.com/netdata/netdata/blob/798c141c49ee85bddc8f48f25d2cb593ec9… https://github.com/netdata/netdata/commit/92327c9ec211bd1616315abcb255861b1… https://github.com/netdata/netdata/pull/4521 https://www.red4sec.com/cve/netdata_json_injection.txt https://github.com/netdata/netdata/blob/798c141c49ee85bddc8f48f25d2cb593ec9… -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1153687] New: Zypper repo name detection broken
by bugzilla_noreply＠novell.com 24 Nov '21

24 Nov '21

http://bugzilla.suse.com/show_bug.cgi?id=1153687 Bug ID: 1153687 Summary: Zypper repo name detection broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- zypper ar obs://some:where/ results in a URL such as https://download.opensuse.org/repositories/some:/where/openSUSE-MicroOS-201… -- You are receiving this mail because: You are on the CC list for the bug.

2 17

[Bug 1160807] New: X fails to start after updating to version 202006 (segfault with radeon driver)
by bugzilla_noreply＠novell.com 23 Nov '21

23 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1160807 Bug ID: 1160807 Summary: X fails to start after updating to version 202006 (segfault with radeon driver) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: schaefer.frank(a)gmx.net QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- After upgrading from an end-of October-version to 202006, X doesn't start anymore. Unfortunately I can't switch back to a working version. Relevant lines in Xorg.o.log (see attachment) seem to be: ... [ 63.275] (EE) Failed to open authorization file "/run/sddm/{cc28ba16-c77b-499a-a4d5-86c4ea584c2c}": No such file or directory [ 63.593] (EE) [ 63.593] (EE) Backtrace: [ 63.593] (EE) 0: /usr/bin/X (xorg_backtrace+0x52) [0x66e0f2] [ 63.593] (EE) 1: /usr/bin/X (0x4c7000+0x1aafd2) [0x671fd2] [ 63.593] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb7f6faa4] [ 63.593] (EE) 3: /usr/lib/xorg/modules/drivers/radeon_drv.so (0xb70e1000+0x4863f) [0xb712963f] [ 63.594] (EE) 4: /usr/bin/X (miSyncInitFence+0x6c) [0x642e9c] [ 63.594] (EE) 5: /usr/bin/X (0x4c7000+0x17c700) [0x643700] [ 63.594] (EE) 6: /usr/bin/X (0x4c7000+0xdf501) [0x5a6501] [ 63.594] (EE) 7: /usr/bin/X (0x4c7000+0x17813c) [0x63f13c] [ 63.594] (EE) 8: /usr/bin/X (0x4c7000+0x469f6) [0x50d9f6] [ 63.594] (EE) 9: /usr/bin/X (0x4c7000+0x4aeeb) [0x511eeb] [ 63.594] (EE) 10: /usr/bin/X (0x4c7000+0x33f5b) [0x4faf5b] [ 63.594] (EE) 11: /lib/libc.so.6 (__libc_start_main+0xf1) [0xb7738ec1] [ 63.594] (EE) 12: /usr/bin/X (_start+0x31) [0x4fafa1] [ 63.594] (EE) [ 63.594] (EE) Segmentation fault at address 0x8 [ 63.594] (EE) Fatal server error: [ 63.594] (EE) Caught signal 11 (Segmentation fault). Server aborting ... Might be related to bug 1160637. Differences are: - my graphics card (HD6570) uses the older "radeon" driver instead of "amdgpu" - stack trace looks a bit different - I'm using a 32 bit installation - result is segfault (signal 11) instead of abort (signal 6) After the segfault, X restart seems to be triggered automatically, resulting in an endless loop (X restart - segfault - X restart - segfault - ...). That might be a separate bug. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1160723] New: haveged fails to load
by bugzilla_noreply＠novell.com 23 Nov '21

23 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1160723 Bug ID: 1160723 Summary: haveged fails to load Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Not sure, when this behaviour started, but haveged fails to load in the first attempt for some time now. The service gets rescheduled then and in the second attempt the start succeeds. Does the first attempt happen too early? haveged[250]: haveged: listening socket at 3 haveged[250]: haveged: restart in new root: /sysroot systemd[1]: Starting Tell haveged about new root... systemd[1]: haveged-switch-root.service: Succeeded. systemd[1]: Started Tell haveged about new root. haveged[250]: haveged: listening socket at 3 haveged[250]: haveged: Couldn't get poolsize systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Service RestartSec=100ms expired, scheduling restart. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 1. haveged[744]: haveged: listening socket at 3 $ps | grep haveged root 744 1 0 10:39 ? 00:00:00 /usr/sbin/haveged -w 1024 -v 0 -F -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 929755] New: shutter is missing perl(Gnome2) in Tumbleweed
by bugzilla_noreply＠novell.com 21 Nov '21

21 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=929755 Bug ID: 929755 Summary: shutter is missing perl(Gnome2) in Tumbleweed Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: f_koch(a)gmx.de 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/41.0.2272.101 Safari/537.36 Build Identifier: flo@linux-mvsa:~> sudo zypper in shutter Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides perl(Gnome2) needed by shutter-0.93.1-1.1.noarch Solution 1: do not install shutter-0.93.1-1.1.noarch Solution 2: break shutter-0.93.1-1.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1160097] New: Yast2 print fails to stop cups
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1160097 Bug ID: 1160097 Summary: Yast2 print fails to stop cups Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: jsmeix(a)suse.com Found By: --- Blocker: --- On a fresh installed openSUSE Tumbleweed installation I tried to configure printing from another cups server. The printer module can find the cups server, but after pressing "ok" the module tried to stop cups service, which failed The related y2log content is shown below: 2020-01-05 11:16:38 <1> localhost.localdomain(12831) [Ruby] modules/Service.rb:186 Stopping service 'cups' 2020-01-05 11:16:38 <1> localhost.localdomain(12831) [Ruby] yast2/systemctl.rb:34 systemctl show cups.service --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --proper ty=FragmentPath --property=CanReload 2020-01-05 11:16:38 <1> localhost.localdomain(12831) [Ruby] yast2/systemctl.rb:34 systemctl stop cups.service 2020-01-05 11:16:38 <3> localhost.localdomain(12831) [bash] ShellCommand.cc(shellcommand):78 Warning: Stopping cups.service, but it can still be activated by: 2020-01-05 11:16:38 <3> localhost.localdomain(12831) [bash] ShellCommand.cc(shellcommand):78 cups.socket 2020-01-05 11:16:38 <3> localhost.localdomain(12831) [bash] ShellCommand.cc(shellcommand):78 cups.path Please note that cups service was disabled at this stage, which let systemctl print the last messages. If I enable cups before starting cups printer this issue is gone, which let me think that the yast printer module should make sure, that cups is enabled before stopping. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1165517] New: lldb has a wrong version string
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1165517 Bug ID: 1165517 Summary: lldb has a wrong version string Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- $ lldb -v lldb version 9.0.1 ( revision %{_llvm_revision}) -- You are receiving this mail because: You are on the CC list for the bug.

2 3