Vulnerabilidades

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu: NULL-check BO&amp;#39;s backing store when determining GFX12 PTE flags<br /> <br /> PRT BOs may not have any backing store, so bo-&gt;tbo.resource will be<br /> NULL. Check for that before dereferencing.<br /> <br /> (cherry picked from commit 3e3fcd29b505cebed659311337ea03b7698767fc)

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes<br /> <br /> Currently, load_microcode_amd() iterates over all NUMA nodes, retrieves their<br /> CPU masks and unconditionally accesses per-CPU data for the first CPU of each<br /> mask.<br /> <br /> According to Documentation/admin-guide/mm/numaperf.rst:<br /> <br /> "Some memory may share the same node as a CPU, and others are provided as<br /> memory only nodes."<br /> <br /> Therefore, some node CPU masks may be empty and wouldn&amp;#39;t have a "first CPU".<br /> <br /> On a machine with far memory (and therefore CPU-less NUMA nodes):<br /> - cpumask_of_node(nid) is 0<br /> - cpumask_first(0) is CONFIG_NR_CPUS<br /> - cpu_data(CONFIG_NR_CPUS) accesses the cpu_info per-CPU array at an<br /> index that is 1 out of bounds<br /> <br /> This does not have any security implications since flashing microcode is<br /> a privileged operation but I believe this has reliability implications by<br /> potentially corrupting memory while flashing a microcode update.<br /> <br /> When booting with CONFIG_UBSAN_BOUNDS=y on an AMD machine that flashes<br /> a microcode update. I get the following splat:<br /> <br /> UBSAN: array-index-out-of-bounds in arch/x86/kernel/cpu/microcode/amd.c:X:Y<br /> index 512 is out of range for type &amp;#39;unsigned long[512]&amp;#39;<br /> [...]<br /> Call Trace:<br /> dump_stack<br /> __ubsan_handle_out_of_bounds<br /> load_microcode_amd<br /> request_microcode_amd<br /> reload_store<br /> kernfs_fop_write_iter<br /> vfs_write<br /> ksys_write<br /> do_syscall_64<br /> entry_SYSCALL_64_after_hwframe<br /> <br /> Change the loop to go over only NUMA nodes which have CPUs before determining<br /> whether the first CPU on the respective node needs microcode update.<br /> <br /> [ bp: Massage commit message, fix typo. ]

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> HID: ignore non-functional sensor in HP 5MP Camera<br /> <br /> The HP 5MP Camera (USB ID 0408:5473) reports a HID sensor interface that<br /> is not actually implemented. Attempting to access this non-functional<br /> sensor via iio_info causes system hangs as runtime PM tries to wake up<br /> an unresponsive sensor.<br /> <br /> [453] hid-sensor-hub 0003:0408:5473.0003: Report latency attributes: ffffffff:ffffffff<br /> [453] hid-sensor-hub 0003:0408:5473.0003: common attributes: 5:1, 2:1, 3:1 ffffffff:ffffffff<br /> <br /> Add this device to the HID ignore list since the sensor interface is<br /> non-functional by design and should not be exposed to userspace.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iscsi_ibft: Fix UBSAN shift-out-of-bounds warning in ibft_attr_show_nic()<br /> <br /> When performing an iSCSI boot using IPv6, iscsistart still reads the<br /> /sys/firmware/ibft/ethernetX/subnet-mask entry. Since the IPv6 prefix<br /> length is 64, this causes the shift exponent to become negative,<br /> triggering a UBSAN warning. As the concept of a subnet mask does not<br /> apply to IPv6, the value is set to ~0 to suppress the warning message.

*** Pendiente de traducción *** Crypt::Salt for Perl version 0.01 uses insecure rand() function when generating salts for cryptographic purposes.

*** Pendiente de traducción *** A flaw was found in the Tempo Operator. When the Jaeger UI Monitor Tab functionality is enabled in a Tempo instance managed by the Tempo Operator, the Operator creates a ClusterRoleBinding for the Service Account of the Tempo instance to grant the cluster-monitoring-view ClusterRole.<br /> This can be exploited if a user has &amp;#39;create&amp;#39; permissions on TempoStack and &amp;#39;get&amp;#39; permissions on Secret in a namespace (for example, a user has ClusterAdmin permissions for a specific namespace), as the user can read the token of the Tempo service account and therefore has access to see all cluster metrics.

*** Pendiente de traducción *** A flaw was found in Tempo Operator, where it creates a ServiceAccount, ClusterRole, and ClusterRoleBinding when a user deploys a TempoStack or TempoMonolithic instance. This flaw allows a user with full access to their namespace to extract the ServiceAccount token and use it to submit TokenReview and SubjectAccessReview requests, potentially revealing information about other users&amp;#39; permissions. While this does not allow privilege escalation or impersonation, it exposes information that could aid in gathering information for further attacks.

*** Pendiente de traducción *** The Video Url plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the &amp;#39;id&amp;#39; parameter in all versions up to, and including, 1.0.0.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

*** Pendiente de traducción *** The Advanced Search by My Solr Server plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.5. This is due to missing or incorrect nonce validation on the &amp;#39;MySolrServerSettings&amp;#39; page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

*** Pendiente de traducción *** The Front End Users plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the file uploads field of the registration form in all versions up to, and including, 3.2.32. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site&amp;#39;s server which may make remote code execution possible.

*** Pendiente de traducción *** The Gift Certificate Creator plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘receip_address’ parameter in all versions up to, and including, 1.1.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

*** Pendiente de traducción *** The Smart Icons For WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 1.0.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Editor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.