Vulnerabilidades

*** Pendiente de traducción *** xrdp is an open source RDP server. In versions 0.10.6 and prior, when an authenticated user session is initialized using the Xvnc backend over UNIX domain sockets, the Xvnc process is launched with insufficient authentication mechanisms. A local authenticated attacker could exploit this vulnerability to bypass intended session isolation, allowing them to unauthorizedly view or control the active desktop sessions of other users on the same system. Users using other backends, such as xorgxrdp or Xvnc over TCP sockets, are not affected. This issue has been fixed in version 0.10.6.1.

*** Pendiente de traducción *** xrdp is an open source RDP server. Versions 0.10.6 and prior contain a vulnerability concerning the parsing of Client Security Data within the Client MCS Connect Initial PDU with GCC Conference Create Request during the connection sequence. During the initial capability and security negotiation phase, the parser fails to perform sufficient length validation for the incoming data block. A remote, unauthenticated attacker could potentially exploit this flaw by sending a specially crafted RDP packet containing malformed data. Due to missing bounds checks, the xrdp process may read a small number of bytes beyond the declared data block boundary, potentially disclosing process memory contents that could be combined with other vulnerabilities. This issue has been fixed in version 0.10.6.1.

*** Pendiente de traducción *** FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. Prior to version 1.8.221, FreeScout's attachment download route skips token authentication for any attachment whose `token_type` is set to `1` (`TOKEN_TYPE_LEGACY`). Because this route is unauthenticated and the file path is deterministic, an unauthenticated remote attacker can download any attachment that was created by an older version of FreeScout without possessing a valid token or session. Version 1.8.221 contains a fix.

*** Pendiente de traducción *** FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. Prior to version 1.8.219, the open tracking endpoint `GET /thread/read/{conversation_id}/{thread_id}` allows unauthenticated attackers to enumerate valid conversation and thread IDs, and modify thread state (`opened_at` timestamp) without any authentication. Version 1.8.219 patches the issue.

*** Pendiente de traducción *** Flask-Security-Too allows users to add security features to their Flask applicationa. Version 5.8.0's OAuth reauthentication flow can mark a session as fresh after verifying an OAuth account that belongs to a different user. If an attacker can operate an already-authenticated but stale victim session, they can complete OAuth verification using their own OAuth identity. The victim session is then treated as recently reauthenticated, allowing freshness-protected account actions to proceed. Version 5.8.1 contains a fix for this issue.

*** Pendiente de traducción *** RT is an open source, enterprise-grade issue and ticket tracking system. Versions 6.0.0 and above, prior to 6.0.3 contain a reflected Cross-Site Scripting (XSS) vulnerability. An attacker who can induce an authenticated RT user to visit a crafted URL can execute arbitrary JavaScript in that user's browser session. There are no effective workarounds. Avoid following untrusted RT URLs. This issue has been fixed in version 6.0.3.

*** Pendiente de traducción *** RT is an open source, enterprise-grade issue and ticket tracking system. Versions 6.0.0 and above, prior to 6.0.3, contain a stored Cross-Site Scripting (XSS) vulnerability, where user-controlled data is rendered without proper HTML escaping. An authenticated user with permission to set the relevant data can inject JavaScript that executes when another RT user views the affected page. This issue has been fixed in version 6.0.3.

*** Pendiente de traducción *** Chamilo version 1.11.40 and earlier are vulnerable to authenticated remote code execution in the main/inc/ajax/lang.ajax.php path. This endpoint is protected only by `api_protect_course_script(true)`, which means any authenticated user enrolled in a course (student, teacher, DRH) can reach it.

*** Pendiente de traducción *** Chamilo LMS versions 1.11.38 and earlier contain a stored cross-site scripting vulnerability in the user registration form that allows any unauthenticated attacker to execute arbitrary JavaScript in an administrator's browser session, leading to full platform admin account takeover. This has been patched in 1.11.40.

*** Pendiente de traducción *** Mettle SendPortal 3.0.1 and earlier contains a stored cross-site scripting (XSS) vulnerability in the template management functionality. The application fails to properly sanitize user-supplied input in the content parameter of the /templates endpoint, allowing an attacker to persistently inject malicious JavaScript code that is executed in the browsers of users who access the affected template.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: team: fix NULL pointer dereference in team_xmit during mode change<br /> <br /> __team_change_mode() clears team-&gt;ops with memset() before restoring<br /> safe dummy handlers via team_adjust_ops(). A concurrent team_xmit()<br /> running under RCU on another CPU can read team-&gt;ops.transmit during<br /> this window and call a NULL function pointer, crashing the kernel.<br /> <br /> The race requires a mode change (CAP_NET_ADMIN) concurrent with<br /> transmit on the team device.<br /> <br /> BUG: kernel NULL pointer dereference, address: 0000000000000000<br /> Oops: 0010 [#1] SMP KASAN NOPTI<br /> RIP: 0010:0x0<br /> Call Trace:<br /> team_xmit (drivers/net/team/team_core.c:1853)<br /> dev_hard_start_xmit (net/core/dev.c:3904)<br /> __dev_queue_xmit (net/core/dev.c:4871)<br /> packet_sendmsg (net/packet/af_packet.c:3109)<br /> __sys_sendto (net/socket.c:2265)<br /> <br /> The original code assumed that no ports means no traffic, so mode<br /> changes could freely memset()/memcpy() the ops. AF_PACKET with<br /> forced carrier breaks that assumption.<br /> <br /> Prevent the race instead of making it safe: replace memset()/memcpy()<br /> with per-field updates that never touch transmit or receive. Those<br /> two handlers are managed solely by team_adjust_ops(), which already<br /> installs dummies when tx_en_port_count == 0 (always true during mode<br /> change since no ports are present). WRITE_ONCE/READ_ONCE prevent<br /> store/load tearing on the handler pointers.<br /> <br /> synchronize_net() before exit_op() drains in-flight readers that may<br /> still reference old mode state from before port removal switched the<br /> handlers to dummies.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized<br /> <br /> When CONFIG_BPF_LSM=y is set, BPF inode storage maps<br /> (BPF_MAP_TYPE_INODE_STORAGE) are compiled into the kernel. However,<br /> if the BPF LSM is not explicitly enabled at boot time (e.g. omitted<br /> from the "lsm=" boot parameter), lsm_prepare() is never executed for<br /> the BPF LSM.<br /> <br /> Consequently, the BPF inode security blob offset<br /> (bpf_lsm_blob_sizes.lbs_inode) is never initialized and remains at<br /> its default compiled size of 8 bytes instead of being updated to a<br /> valid offset past the reserved struct rcu_head (typically 16 bytes<br /> or more).<br /> <br /> When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGE<br /> map, bpf_inode() evaluates inode-&gt;i_security + 8. This erroneously<br /> aliases the struct rcu_head.func callback pointer at the beginning<br /> of the inode-&gt;i_security blob. During subsequent map element cleanup<br /> or inode destruction, writing NULL to owner_storage clears the queued<br /> RCU callback pointer. When rcu_do_batch() later executes the queued<br /> callback, it attempts an instruction fetch at address 0x0, triggering<br /> an immediate kernel panic.<br /> <br /> Fix this by introducing a global bpf_lsm_initialized boolean flag<br /> marked with __ro_after_init. Set this flag to true inside bpf_lsm_init()<br /> when the LSM framework successfully registers the BPF LSM. Gate map<br /> allocation in inode_storage_map_alloc() on this flag, returning<br /> -EOPNOTSUPP if the BPF LSM is in turn uninitialized.<br /> <br /> This fail-fast approach prevents userspace from allocating inode<br /> storage maps when the supporting BPF LSM infrastructure is absent,<br /> avoiding zombie map states.