Vulnerabilities

A vulnerability classified as problematic was found in misstt123 oasys 1.0. Affected by this vulnerability is the function image of the file /show. The manipulation leads to path traversal. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable.

A vulnerability, which was classified as problematic, has been found in misstt123 oasys 1.0. Affected by this issue is some unknown functionality of the component Sticky Notes Handler. The manipulation leads to cross-site request forgery. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available.

A vulnerability, which was classified as problematic, was found in mirweiye Seven Bears Library CMS 2023. This affects an unknown part of the component Background Management Page. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

A vulnerability classified as critical has been found in code-projects Patient Record Management System 1.0. Affected is an unknown function of the file /edit_fpatient.php. The manipulation of the argument ID leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

A vulnerability was found in Xianqi Kindergarten Management System 2.0 Bulid 20190808. It has been rated as critical. This issue affects some unknown processing of the file stu_list.php of the component Child Management. The manipulation of the argument sex leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.

A vulnerability was found in PCMan FTP Server 2.0.7. It has been classified as critical. This affects an unknown part of the component PASV Command Handler. The manipulation leads to buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

A vulnerability was found in PCMan FTP Server 2.0.7. It has been declared as critical. This vulnerability affects unknown code of the component SIZE Command Handler. The manipulation leads to buffer overflow. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Missing Authorization vulnerability in fs-code FS Poster fs-poster.This issue affects FS Poster: from n/a through

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: xhci: Don&amp;#39;t skip on Stopped - Length Invalid<br /> <br /> Up until commit d56b0b2ab142 ("usb: xhci: ensure skipped isoc TDs are<br /> returned when isoc ring is stopped") in v6.11, the driver didn&amp;#39;t skip<br /> missed isochronous TDs when handling Stoppend and Stopped - Length<br /> Invalid events. Instead, it erroneously cleared the skip flag, which<br /> would cause the ring to get stuck, as future events won&amp;#39;t match the<br /> missed TD which is never removed from the queue until it&amp;#39;s cancelled.<br /> <br /> This buggy logic seems to have been in place substantially unchanged<br /> since the 3.x series over 10 years ago, which probably speaks first<br /> and foremost about relative rarity of this case in normal usage, but<br /> by the spec I see no reason why it shouldn&amp;#39;t be possible.<br /> <br /> After d56b0b2ab142, TDs are immediately skipped when handling those<br /> Stopped events. This poses a potential problem in case of Stopped -<br /> Length Invalid, which occurs either on completed TDs (likely already<br /> given back) or Link and No-Op TRBs. Such event won&amp;#39;t be recognized<br /> as matching any TD (unless it&amp;#39;s the rare Link TRB inside a TD) and<br /> will result in skipping all pending TDs, giving them back possibly<br /> before they are done, risking isoc data loss and maybe UAF by HW.<br /> <br /> As a compromise, don&amp;#39;t skip and don&amp;#39;t clear the skip flag on this<br /> kind of event. Then the next event will skip missed TDs. A downside<br /> of not handling Stopped - Length Invalid on a Link inside a TD is<br /> that if the TD is cancelled, its actual length will not be updated<br /> to account for TRBs (silently) completed before the TD was stopped.<br /> <br /> I had no luck producing this sequence of completion events so there<br /> is no compelling demonstration of any resulting disaster. It may be<br /> a very rare, obscure condition. The sole motivation for this patch<br /> is that if such unlikely event does occur, I&amp;#39;d rather risk reporting<br /> a cancelled partially done isoc frame as empty than gamble with UAF.<br /> <br /> This will be fixed more properly by looking at Stopped event&amp;#39;s TRB<br /> pointer when making skipping decisions, but such rework is unlikely<br /> to be backported to v6.12, which will stay around for a few years.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nfsd: fix legacy client tracking initialization<br /> <br /> Get rid of the nfsd4_legacy_tracking_ops-&gt;init() call in<br /> check_for_legacy_methods(). That will be handled in the caller<br /> (nfsd4_client_tracking_init()). Otherwise, we&amp;#39;ll wind up calling<br /> nfsd4_legacy_tracking_ops-&gt;init() twice, and the second time we&amp;#39;ll<br /> trigger the BUG_ON() in nfsd4_init_recdir().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bcachefs: bch2_ioctl_subvolume_destroy() fixes<br /> <br /> bch2_evict_subvolume_inodes() was getting stuck - due to incorrectly<br /> pruning the dcache.<br /> <br /> Also, fix missing permissions checks.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: xhci: Apply the link chain quirk on NEC isoc endpoints<br /> <br /> Two clearly different specimens of NEC uPD720200 (one with start/stop<br /> bug, one without) were seen to cause IOMMU faults after some Missed<br /> Service Errors. Faulting address is immediately after a transfer ring<br /> segment and patched dynamic debug messages revealed that the MSE was<br /> received when waiting for a TD near the end of that segment:<br /> <br /> [ 1.041954] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ffa08fe0<br /> [ 1.042120] xhci_hcd: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffa09000 flags=0x0000]<br /> [ 1.042146] xhci_hcd: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffa09040 flags=0x0000]<br /> <br /> It gets even funnier if the next page is a ring segment accessible to<br /> the HC. Below, it reports MSE in segment at ff1e8000, plows through a<br /> zero-filled page at ff1e9000 and starts reporting events for TRBs in<br /> page at ff1ea000 every microframe, instead of jumping to seg ff1e6000.<br /> <br /> [ 7.041671] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ff1e8fe0<br /> [ 7.041999] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ff1e8fe0<br /> [ 7.042011] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint<br /> [ 7.042028] xhci_hcd: All TDs skipped for slot 1 ep 2. Clear skip flag.<br /> [ 7.042134] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint<br /> [ 7.042138] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 31<br /> [ 7.042144] xhci_hcd: Looking for event-dma 00000000ff1ea040 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820<br /> [ 7.042259] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint<br /> [ 7.042262] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 31<br /> [ 7.042266] xhci_hcd: Looking for event-dma 00000000ff1ea050 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820<br /> <br /> At some point completion events change from Isoch Buffer Overrun to<br /> Short Packet and the HC finally finds cycle bit mismatch in ff1ec000.<br /> <br /> [ 7.098130] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13<br /> [ 7.098132] xhci_hcd: Looking for event-dma 00000000ff1ecc50 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820<br /> [ 7.098254] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13<br /> [ 7.098256] xhci_hcd: Looking for event-dma 00000000ff1ecc60 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820<br /> [ 7.098379] xhci_hcd: Overrun event on slot 1 ep 2<br /> <br /> It&amp;#39;s possible that data from the isochronous device were written to<br /> random buffers of pending TDs on other endpoints (either IN or OUT),<br /> other devices or even other HCs in the same IOMMU domain.<br /> <br /> Lastly, an error from a different USB device on another HC. Was it<br /> caused by the above? I don&amp;#39;t know, but it may have been. The disk<br /> was working without any other issues and generated PCIe traffic to<br /> starve the NEC of upstream BW and trigger those MSEs. The two HCs<br /> shared one x1 slot by means of a commercial "PCIe splitter" board.<br /> <br /> [ 7.162604] usb 10-2: reset SuperSpeed USB device number 3 using xhci_hcd<br /> [ 7.178990] sd 9:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s<br /> [ 7.179001] sd 9:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 04 02 ae 00 00 02 00 00<br /> [ 7.179004] I/O error, dev sdb, sector 67284480 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0<br /> <br /> Fortunately, it appears that this ridiculous bug is avoided by setting<br /> the chain bit of Link TRBs on isochronous rings. Other ancient HCs are<br /> known which also expect the bit to be set and they ignore Link TRBs if<br /> it&amp;#39;s not. Reportedly, 0.95 spec guaranteed that the bit is set.<br /> <br /> The bandwidth-starved NEC HC running a 32KB/uframe UVC endpoint reports<br /> tens of MSEs per second and runs into the bug within seconds. Chaining<br /> Link TRBs allows the same workload to run for many minutes, many times.<br /> <br /> No ne<br /> ---truncated---