CVE Vulnerability Catalog

XSS vulnerability in the web-based management interface of Cisco Unified Communications Manager (Unified CM) and Unified CM SME. An authenticated remote attacker can inject malicious code into specific pages, allowing script execution in the interface context or access to sensitive browser information.

XSS vulnerability in the web-based management interface of Cisco Cyber Vision Center. An authenticated remote attacker can inject malicious code into specific pages, allowing script execution in the interface context or access to sensitive browser information. The attacker must have valid administrative credentials with access to the Reports page.

A vulnerability in the web-based management interface of Cisco Cyber Vision Center is due to insufficient validation of user-supplied input. An authenticated, remote attacker could inject malicious code into specific pages of the interface and conduct cross-site scripting (XSS) attacks.

In Rust from 1.87.0 to before 1.89.0, the tier 3 Cygwin target (x86_64-pc-cygwin) mishandled path separators, causing the standard library's Path API to ignore path components separated by backslashes. Programs compiled for Cygwin that validate paths could misbehave, potentially allowing path traversal attacks or malicious filesystem operations. Rust 1.89.0 fixes this.

Improper handling of symbolic links in the TeamViewer Full Client and Host for Windows — in versions prior to 15.70 of TeamViewer Remote and Tensor — allows an attacker with local, unprivileged access to a device lacking adequate malware protection to escalate privileges by spoofing the update file path. This may result in unauthorized access to sensitive information.

A Stored Cross-Site Scripting (XSS) vulnerability in Issabel v5.0.0. It consists of a stored XSS due to a lack of proper validation of user input through the 'numero_conferencia' parameter in '/index.php?menu=conferencia'.

Issabel v5.0.0 contains a stored Cross-Site Scripting (XSS) vulnerability due to lack of proper validation of user input in the 'email' parameter in '/index.php?menu=address_book'.

In the Linux kernel, the gs_usb driver has a time stamp counter initialization flaw that can lead to a NULL pointer dereference. The issue occurs when the driver is unloaded or unbound before the interface is shut down, and received CAN frames are processed before the timecounter infrastructure is set up. The fix moves initialization before URB submission and converts it from per-channel to per-device.

In the Linux kernel, a refcount leak exists in del_mtd_device() within the MTD subsystem. The function clears mtd->dev before calling of_node_put(), so the device_node reference is never released. This results in unbalanced reference counting and a memory leak.

In the Linux kernel, in the NTFS3 filesystem (fs/ntfs3), there is a memory leak on the error path in ntfs_fill_super(). The fix frees mount options on error, eliminating the leak.

In the Linux kernel, in the hisilicon/hpre cryptographic driver, the hpre_remove() function may return directly after a failed sriov disable operation, leading to resource leak. The fix continues to release remaining resources even after an error.

In the Linux kernel, genelink's genl_bind() invokes the bind() callback even when capability checks fail and -EPERM is returned. Callbacks can therefore run on behalf of unauthorized callers while the syscall still returns failure.

In the Linux kernel, the CAN J1939 protocol lacked a NETDEV_UNREGISTER notification handler, causing issues with network interface unregistration (e.g., vcan0). This led to hangs in unregister_netdevice due to unreleased references.

In the Linux kernel qcom bam_dma dmaengine driver, error handling for missing clock and num-channels in the device tree lacks return statements. This can lead to unsafe reading of channel count from registers and early boot crashes.

In the Linux kernel, the spi-microchip-core-qspi driver incorrectly checked op->max_freq in mchp_coreqspi_supports_op(). During probe op->max_freq is zero, causing a division by zero that sets baud_rate_val to INT_MAX and makes probing of the attached memory device fail.

In the Linux kernel, the do_validate_mem() function lacks error handling for the add_interval() call. If kmalloc() fails in add_interval(), it could result in a null pointer being inserted into the linked list, leading to illegal memory access when sub_interval() is called next.

In the Linux kernel mm/damon/reclaim module, the min_age_region calculation uses aggr_interval as a divisor, which may lead to division-by-zero errors. The fix returns -EINVAL in such cases.

In the Linux kernel, a potential deadlock exists due to reversed locking order between &pl->state_mutex and &phy->lock in phy_config_inband() called by phylink. The issue was detected by lockdep and involves a race between phylink_resolve() and phy_link_up()/phy_link_down(). The fix transfers locking responsibility to the phylink layer.

In the Linux kernel, a fault injection during chunk allocation in trace_pid_write could trigger a warning about double registration of the sched_switch tracepoint. The issue only occurs in crash-like scenarios, but failure handling was added to trace_pid_list_set to suppress the warning.

In the Linux kernel, nfs/localio fails to restore credentials before releasing pageio data. If the nfsd filecache code releases the nfsd_file immediately, it can trigger BUG_ON(cred == current->cred) in __put_cred().