February 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213073] New: clang13-devel from Backports not installable on SLES 15 SP5
by bugzilla_noreply＠suse.com 18 Apr '24

18 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1213073 Bug ID: 1213073 Summary: clang13-devel from Backports not installable on SLES 15 SP5 Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: amoog(a)psi.de QA Contact: packagehub-bugs(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Trying to install clang13-devel from the Backports repository results in: :~ -> sudo zypper install clang13-devel Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'clang-tools >= 13.0.1' needed by the to be installed clang13-devel-13.0.1-bp155.6.38.x86_64 Solution 1: do not install clang13-devel-13.0.1-bp155.6.38.x86_64 Solution 2: break clang13-devel-13.0.1-bp155.6.38.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): ^C Is there some other repository I am missing? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217749] New: No bass in built-in speakers on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 17 Apr '24

17 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1217749 Bug ID: 1217749 Summary: No bass in built-in speakers on Lenovo Slim 7 16" AMD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: variable_valuables761(a)simplelogin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871116 --> https://bugzilla.suse.com/attachment.cgi?id=871116&action=edit Output of "hwinfo --sound" for Lenovo 16ARH7 It seems the bass speakers do not work in the latest Tumbleweed KDE snapshot on the Lenovo Slim 7 16" AMD, 16ARH7, 82UX0001US (and this same model is called Yoga outside the United States). This issue appears to be similar to that of the wide range of recently released laptops that have the CS35L41 and TAS2781 amps, however I cannot find that hardware listed in any of my logs or online spec sheets for this laptop. The closest I can find is that is has a Realtek ALC3287 codec. Attached is the output of "hwinfo --sound" Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1213159] New: [request] Lock root account by default
by bugzilla_noreply＠suse.com 17 Apr '24

17 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1213159 Bug ID: 1213159 Summary: [request] Lock root account by default Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: milachew(a)mail.lv QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since MicroOS aims to keep administration as small as possible, it makes sense to consider blocking root account by default. Original comment: https://www.reddit.com/r/openSUSE/comments/14u7ka1/comment/jr60ogz/?utm_sou… P.S. By the way, there have already been similar discussions, but regarding ALP: https://bugzilla.opensuse.org/show_bug.cgi?id=1203978 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1217244] New: mathgl fails to build ==> Fatal error occurred, no output PDF file produced!
by bugzilla_noreply＠suse.com 17 Apr '24

17 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1217244 Bug ID: 1217244 Summary: mathgl fails to build ==> Fatal error occurred, no output PDF file produced! Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello mathgl does not build on Leap 15.6. This should be fixed before Beta (Feb 2023). https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 Build log from Leap 15.6 https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… [ 500s] /home/abuild/rpmbuild/BUILD/mathgl-8.0.1/python3_build/texinfo/samples.texi:142 [ 500s] 6: ==> Fatal error occurred, no output PDF file produced! [ 500s] Transcript written on mathgl_en.log. [ 500s] /usr/bin/texi2dvi: pdfetex exited with bad status, quitting. [ 500s] make[2]: *** [texinfo/CMakeFiles/doc_en.dir/build.make:243: texinfo/mathgl_en.pdf] Error 1 [ 500s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/mathgl-8.0.1/python3_build' [ 500s] make[1]: *** [CMakeFiles/Makefile2:1486: texinfo/CMakeFiles/doc_en.dir/all] Error 2 [ 500s] make: *** [Makefile:139: all] Error 2 [ 500s] error: Bad exit status from /var/tmp/rpm-tmp.nATkRq (%build) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217254] New: python-Django1 fails to build as test_delete_signals fails
by bugzilla_noreply＠suse.com 17 Apr '24

17 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1217254 Bug ID: 1217254 Summary: python-Django1 fails to build as test_delete_signals fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello python-Django1 does not build on Leap 15.6. This should be fixed before Beta (Feb 2023). https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 Build log from Leap 15.6 https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… [ 154s] ====================================================================== [ 154s] FAIL: test_delete_signals (signals.tests.SignalTests) [ 154s] ---------------------------------------------------------------------- [ 154s] Traceback (most recent call last): [ 154s] File "/usr/lib64/python3.6/unittest/case.py", line 59, in testPartExecutor [ 154s] yield [ 154s] File "/usr/lib64/python3.6/unittest/case.py", line 608, in run [ 154s] self.tearDown() [ 154s] File "/home/abuild/rpmbuild/BUILD/Django-1.11.29/tests/signals/tests.py", line 33, in tearDown [ 154s] self.assertEqual(self.pre_signals, post_signals) [ 154s] File "/usr/lib64/python3.6/unittest/case.py", line 829, in assertEqual [ 154s] assertion_func(first, second, msg=msg) [ 154s] File "/usr/lib64/python3.6/unittest/case.py", line 1039, in assertTupleEqual [ 154s] self.assertSequenceEqual(tuple1, tuple2, msg, seq_type=tuple) [ 154s] File "/usr/lib64/python3.6/unittest/case.py", line 1010, in assertSequenceEqual [ 154s] self.fail(msg) [ 154s] File "/usr/lib64/python3.6/unittest/case.py", line 670, in fail [ 154s] raise self.failureException(msg) [ 154s] AssertionError: Tuples differ: (1, 0, 2, 1) != (1, 0, 2, 0) [ 154s] [ 154s] First differing element 3: [ 154s] 1 [ 154s] 0 [ 154s] [ 154s] - (1, 0, 2, 1) [ 154s] ? ^ [ 154s] [ 154s] + (1, 0, 2, 0) [ 154s] ? ^ [ 154s] -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219508] New: autofs stalls at random times
by bugzilla_noreply＠suse.com 17 Apr '24

17 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219508 Bug ID: 1219508 Summary: autofs stalls at random times 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.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872404 --> https://bugzilla.suse.com/attachment.cgi?id=872404&action=edit journal I am using autofs to access NFS resources. In irregular intevals, autofs stalls, which results in hanging processes trying to access autofs-mounted resources. Example: First a "good" case: [ 1292.438345] apollon kernel: autofs_mount_wait:254: autofs4:pid:27516:autofs_mount_wait: waiting for mount name=/ [ 1292.438348] apollon kernel: autofs_wait:419: autofs4:pid:27516:autofs_wait: new wait id = 0x00000006, name = 00000000819633e1, nfy=1 [ 1292.438351] apollon kernel: autofs_notify_daemon:92: autofs4:pid:27516:autofs_notify_daemon: wait id = 0x00000006, name = 00000000819633e1, type=5 [ 1291.740237] apollon automount[12337]: handle_packet: type = 5 [ 1291.740335] apollon automount[12337]: handle_packet_missing_direct: token 6, name /net/ananas.local/export/Public, request pid 27516 [ 1291.740396] apollon automount[12337]: attempting to mount entry /net/ananas.local/export/Public [ 1291.740461] apollon automount[12337]: lookup_mount: lookup(hosts): /net/ananas.local/export/Public -> ananas.local:/export/Public [ 1291.740530] apollon automount[12337]: parse_mount: parse(sun): expanded entry: ananas.local:/export/Public [ 1291.740590] apollon automount[12337]: parse_mount: parse(sun): gathered options: [ 1291.740680] apollon automount[12337]: sun_mount: parse(sun): mounting root /net/ananas.local/export/Public, mountpoint /net/ananas.local/export/Public, what ananas.local:/export/Public, fstype nfs, options nosuid,nodev [ 1291.740750] apollon automount[12337]: mount(nfs): root=/net/ananas.local/export/Public name=/net/ananas.local/export/Public what=ananas.local:/export/Public, fstype=nfs, options=nosuid,nodev [ 1291.740839] apollon automount[12337]: mount(nfs): nfs options="nosuid,nodev", nobind=0, nosymlink=0, ro=0 [ 1291.740905] apollon automount[12337]: get_nfs_info: called with host ananas.local(192.168.1.167) proto 6 version 0x20 [ 1291.740959] apollon automount[12337]: get_nfs_info: nfs v3 rpc ping time: 0.000209 [ 1291.741009] apollon automount[12337]: get_nfs_info: host ananas.local cost 209 weight 0 [ 1291.741072] apollon automount[12337]: get_nfs_info: called with host ananas.local(192.168.1.167) proto 17 version 0x20 [ 1291.741123] apollon automount[12337]: prune_host_list: selected subset of hosts that support NFS3 over TCP [ 1291.741173] apollon automount[12337]: mount_mount: mount(nfs): calling mkdir_path /net/ananas.local/export/Public [ 1291.741209] apollon automount[12337]: mount(nfs): calling mount -t nfs -s -o nosuid,nodev ananas.local:/export/Public /net/ananas.local/export/Public [ 1291.820337] apollon automount[12337]: mount_mount: mount(nfs): mounted ananas.local:/export/Public on /net/ananas.local/export/Public [ 1291.822090] apollon automount[12337]: dev_ioctl_send_ready: token = 6 [ 1291.822434] apollon automount[12337]: mounted /net/ananas.local/export/Public [ 1292.540540] apollon kernel: autofs_mount_wait:256: autofs4:pid:27516:autofs_mount_wait: mount wait done status=0 Shortly later, a similar mount hangs after the "sun_mount: parse(sun): mounting..." message: [ 1342.089949] apollon kernel: autofs_mount_wait:254: autofs4:pid:28784:autofs_mount_wait: waiting for mount name=/ [ 1342.089964] apollon kernel: autofs_wait:419: autofs4:pid:28784:autofs_wait: new wait id = 0x00000007, name = 00000000739379e8, nfy=1 [ 1342.089979] apollon kernel: autofs_notify_daemon:92: autofs4:pid:28784:autofs_notify_daemon: wait id = 0x00000007, name = 00000000739379e8, type=5 [ 1342.090224] apollon kernel: autofs_d_manage:426: autofs4:pid:12348:autofs_d_manage: dentry=000000007ea364a8 ananas.local [ 1342.090251] apollon kernel: autofs_d_manage:426: autofs4:pid:12348:autofs_d_manage: dentry=00000000739379e8 / [ 1342.090264] apollon kernel: autofs_d_manage:426: autofs4:pid:12348:autofs_d_manage: dentry=00000000739379e8 / [ 1341.378250] apollon automount[12337]: handle_packet_missing_direct: token 7, name /net/ananas.local/export/Git, request pid 28784 [ 1341.q378421] apollon automount[12337]: attempting to mount entry /net/ananas.local/export/Git [ 1341.378598] apollon automount[12337]: lookup_mount: lookup(hosts): /net/ananas.local/export/Git -> ananas.local:/export/Git [ 1341.378758] apollon automount[12337]: parse_mount: parse(sun): expanded entry: ananas.local:/export/Git [ 1341.378918] apollon automount[12337]: parse_mount: parse(sun): gathered options: [ 1341.379110] apollon automount[12337]: sun_mount: parse(sun): mounting root /net/ananas.local/export/Git, mountpoint /net/ananas.local/export/Git, what ananas.local:/export/Git, fstype nfs, options nosuid,nodev <-- nothing --> [ 3276.455832] apollon automount[12337]: handle_packet: type = 5 Nothing happens until I noticed and tried to restart "autofs.service", which times out, too: [ 3302.288384] apollon systemd[1]: Stopping Automounts filesystems on demand... [ 3302.289735] apollon automount[12337]: do_notify_state: signal 15 [ 3302.291839] apollon automount[12337]: master_notify_state_change: sig 15 switching /net from 4 to 5 [ 3482.297728] apollon systemd[1]: autofs.service: State 'stop-sigterm' timed out. Killing. [ 3482.989282] apollon kernel: autofs_dentry_release:114: autofs4:pid:28785:autofs_dentry_release: releasing 0000000002d0d9f7 [ 3482.989361] apollon kernel: autofs_dentry_release:114: autofs4:pid:28785:autofs_dentry_release: releasing 00000000d97fdbcf ... [ 3482.305113] apollon systemd[1]: autofs.service: Killing process 12337 (automount) with signal SIGKILL. [ 3482.305203] apollon systemd[1]: autofs.service: Main process exited, code=killed, status=9/KILL [ 3482.305379] apollon systemd[1]: autofs.service: Failed with result 'timeout'. [ 3482.323666] apollon systemd[1]: Stopped Automounts filesystems on demand. The subsequent restart fails as well: [ 3482.364940] apollon systemd[1]: Starting Automounts filesystems on demand... ... [ 3482.383394] apollon automount[933]: Starting automounter version 5.1.8, master map auto.master [ 3482.383955] apollon automount[933]: using kernel protocol version 5.05 [ 3483.262099] apollon kernel: autofs_d_manage:426: autofs4:pid:940:autofs_d_manage: dentry=00000000739379e8 / [ 3483.262108] apollon kernel: autofs_mount_wait:254: autofs4:pid:940:autofs_mount_wait: waiting for mount name=/ [ 3483.262121] apollon kernel: autofs_wait:429: autofs4:pid:940:autofs_wait: existing wait id = 0x00000007, name = 00000000739379e8, nfy=1 [ 3482.579217] apollon automount[933]: parse_mount: parse(sun): dequote(""/export/Git"") -> /export/Git [ 3482.579445] apollon automount[933]: parse_mapent: parse(sun): gathered options: [ 3482.579738] apollon automount[933]: parse_mapent: parse(sun): dequote(""ananas.local:/export/Git"") -> ananas.local:/export/Git [ 3482.579965] apollon automount[933]: update_offset_entry: parse(sun): updated multi-mount offset /export/Git -> ananas.local:/export/Git ... [ 3482.584814] apollon automount[933]: tree_mapent_mount_offset: mount offset /net/ananas.local/export/Backup [ 3482.585019] apollon automount[933]: remount_active_mount: trying to re-connect to mount /net/ananas.local/export/Backup [ 3482.585271] apollon automount[933]: mounted offset on /net/ananas.local/export/Backup with timeout 300, freq 75 seconds [ 3482.585580] apollon automount[933]: remount_active_mount: re-connected to mount /net/ananas.local/export/Backup [ 3482.585848] apollon automount[933]: tree_mapent_mount_offset: mount offset /net/ananas.local/export/Git [ 3557.456823] apollon automount[933]: st_expire: state 0 path /net [ 3558.142739] apollon kernel: autofs_d_manage:426: autofs4:pid:1058:autofs_d_manage: dentry=0000000063ddaa27 zeus.local [ 3558.142778] apollon kernel: autofs_d_manage:426: autofs4:pid:1058:autofs_d_manage: dentry=00000000c3906c58 / [ 3558.142881] apollon kernel: autofs_direct_busy:155: autofs4:pid:1058:autofs_direct_busy: top 00000000c3906c58 / [ 3557.462849] apollon automount[933]: state.c:690: assertion failed: ap->state == ST_READY [ 3557.462914] apollon automount[933]: expire_proc: exp_proc = 140512157763264 path /net [ 3557.462985] apollon automount[933]: expire_proc_indirect: expire /net/zeus.local/mnt/git [ 3557.463041] apollon automount[933]: expire_proc_indirect: expire /net/zeus.local [ 3662.547687] apollon systemd[1]: autofs.service: start operation timed out. Terminating. [ 3842.797526] apollon systemd[1]: autofs.service: State 'stop-sigterm' timed out. Killing. [ 3842.798330] apollon systemd[1]: autofs.service: Killing process 933 (automount) with signal SIGKILL. [ 3843.479204] apollon kernel: autofs_mount_wait:256: autofs4:pid:940:autofs_mount_wait: mount wait done status=-4 [ 3843.480412] apollon kernel: autofs_dentry_release:114: autofs4:pid:940:autofs_dentry_release: releasing 00000000b3646c6f [ 3843.480418] apollon kernel: autofs_dentry_release:114: autofs4:pid:940:autofs_dentry_release: releasing 0000000039d15e2f [ 3842.800405] apollon systemd[1]: autofs.service: Main process exited, code=killed, status=9/KILL [ 3842.800493] apollon systemd[1]: autofs.service: Failed with result 'timeout'. [ 3842.830035] apollon systemd[1]: Failed to start Automounts filesystems on demand. [ 3842.831266] apollon systemd[1]: autofs.service: Consumed 4min 45.195s CPU time. Full journal attached. At the time of the failure (and afterwards), I see the following related mounts: apollon:~ # mount -t nfs4 zeus.local:/mnt/git on /net/zeus.local/mnt/git type nfs4 (rw,nosuid,nodev,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.30.40,local_lock=none,addr=192.168.30.20) ananas.local:/export/vms on /net/ananas.local/export/vms type nfs4 (rw,nosuid,nodev,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.40,local_lock=none,addr=192.168.1.167) ananas.local:/export/Public on /net/ananas.local/export/Public type nfs4 (rw,nosuid,nodev,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.40,local_lock=none,addr=192.168.1.167) apollon:~ # mount -t autofs systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=32,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=1614) -hosts on /net type autofs (rw,relatime,fd=6,pgrp=933,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=170192) -hosts on /net/zeus.local/home type autofs (rw,relatime,fd=6,pgrp=933,timeout=300,minproto=5,maxproto=5,offset,pipe_ino=170192) -hosts on /net/zeus.local/mnt/git type autofs (rw,relatime,fd=6,pgrp=933,timeout=300,minproto=5,maxproto=5,offset,pipe_ino=170192) -hosts on /net/zeus.local/mnt/nv type autofs (rw,relatime,fd=6,pgrp=933,timeout=300,minproto=5,maxproto=5,offset,pipe_ino=170192) -hosts on /net/ananas.local/export/Backup type autofs (rw,relatime,fd=-1,pgrp=933,timeout=300,minproto=5,maxproto=5,offset,pipe_ino=-1) -hosts on /net/ananas.local/export/Git type autofs (rw,relatime,fd=6,pgrp=12337,timeout=300,minproto=5,maxproto=5,offset,pipe_ino=71571) -hosts on /net/ananas.local/export/Media type autofs (rw,relatime,fd=6,pgrp=12337,timeout=300,minproto=5,maxproto=5,offset,pipe_ino=71571) -hosts on /net/ananas.local/export/Public type autofs (rw,relatime,fd=6,pgrp=12337,timeout=300,minproto=5,maxproto=5,offset,pipe_ino=71571) -hosts on /net/ananas.local/export/Wilck type autofs (rw,relatime,fd=-1,pgrp=12337,timeout=300,minproto=5,maxproto=5,offset,pipe_ino=-1) -hosts on /net/ananas.local/export/home type autofs (rw,relatime,fd=6,pgrp=12337,timeout=300,minproto=5,maxproto=5,offset,pipe_ino=71571) -hosts on /net/ananas.local/export/vms type autofs (rw,relatime,fd=6,pgrp=12337,timeout=300,minproto=5,maxproto=5,offset,pipe_ino=71571) Both nfs servers (ananas.local and zeus.local) are running openSUSE Leap 15.5. I am seeing this kind of stalls only on my tumbleweed system. For a long time I'd thought that the problems were caused by the SUSE VPN somehow interfering with autofs, but I the case documented here was observed without VPN active. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1214027] New: All user may connect to this network should not be enable by default
by bugzilla_noreply＠suse.com 16 Apr '24

16 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214027 Bug ID: 1214027 Summary: All user may connect to this network should not be enable by default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: cosmin.tanczel(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Whenever a new connection is created using the network manager applet in KDE, the option "All user may connect to this network" should not be enabled by default. Reasoning: 1. Security - there are users that just input the root password so the created connection is available for everybody, even though this should not be the case. (I know, if the user has root access he should know what he's doing, but still) 2. Unnecessary step in the creation of a new connection process. Might be there is a reasoning to have it enabled by default, so please let me know if this is the case. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1214176] New: VUL-0: CVE-2023-39959: nextcloud: calendar or address book existence leak via DAV
by bugzilla_noreply＠suse.com 16 Apr '24

16 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214176 Bug ID: 1214176 Summary: VUL-0: CVE-2023-39959: nextcloud: calendar or address book existence leak via DAV Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/374996/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: ecsos(a)schirra.net Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CVE-2023-39959 Nextcloud Server provides data storage for Nextcloud, an open source cloud platform. Starting in version 25.0.0 and prior to versions 25.0.9, 26.0.4, and 27.0.1, unauthenticated users could send a DAV request which reveals whether a calendar or an address book with the given identifier exists for the victim. Nextcloud Server versions 25.0.9, 26.0.4, and 27.0.1 and Nextcloud Enterprise Server versions 25.0.9, 26.0.4, and 27.0.1 contain a patch for this issue. No known workarounds are available. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39959 https://www.cve.org/CVERecord?id=CVE-2023-39959 https://github.com/nextcloud/security-advisories/security/advisories/GHSA-g… https://github.com/nextcloud/server/pull/38747 https://hackerone.com/reports/1832126 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1214175] New: VUL-0: CVE-2023-39958: nextcloud: missing bruteforce protection for client secrets of configured OAuth2 clients
by bugzilla_noreply＠suse.com 16 Apr '24

16 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214175 Bug ID: 1214175 Summary: VUL-0: CVE-2023-39958: nextcloud: missing bruteforce protection for client secrets of configured OAuth2 clients Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/374995/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: ecsos(a)schirra.net Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CVE-2023-39958 Nextcloud Server provides data storage for Nextcloud, an open source cloud platform. Starting in version 22.0.0 and prior to versions 22.2.10.13, 23.0.12.8, 24.0.12.5, 25.0.9, 26.0.4, and 27.0.1, missing protection allows an attacker to brute force the client secrets of configured OAuth2 clients. Nextcloud Server versions 25.0.9, 26.0.4, and 27.0.1 and Nextcloud Enterprise Server versions 22.2.10.13, 23.0.12.8, 24.0.12.5, 25.0.9, 26.0.4, and 27.0.1 contain a patch for this issue. No known workarounds are available. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39958 https://www.cve.org/CVERecord?id=CVE-2023-39958 https://github.com/nextcloud/security-advisories/security/advisories/GHSA-v… https://github.com/nextcloud/server/pull/38773 https://hackerone.com/reports/1258448 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1214177] New: VUL-0: CVE-2023-39961: nextcloud: image download restriction bypass
by bugzilla_noreply＠suse.com 16 Apr '24

16 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214177 Bug ID: 1214177 Summary: VUL-0: CVE-2023-39961: nextcloud: image download restriction bypass Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/374997/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: ecsos(a)schirra.net Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CVE-2023-39961 Nextcloud Server provides data storage for Nextcloud, an open source cloud platform. Starting in version 24.0.4 and prior to versions 25.0.9, 26.0.4, and 27.0.1, when a folder with images or an image was shared without download permissions, the user could add the image inline into a text file and download it. Nextcloud Server versions 25.0.9, 26.0.4, and 27.0.1 and Nextcloud Enterprise Server versions 24.0.12.5, 25.0.9, 26.0.4, and 27.0.1 contain a patch for this issue. No known workarounds are available. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39961 https://www.cve.org/CVERecord?id=CVE-2023-39961 https://github.com/nextcloud/security-advisories/security/advisories/GHSA-q… https://github.com/nextcloud/text/pull/4481 https://hackerone.com/reports/1965156 -- You are receiving this mail because: You are on the CC list for the bug.

1 1