OpenTelemetry-Go versions from 1.0.0-RC1 up to 1.47.0 contain a vulnerability in baggage.Parse and propagation.Baggage.Extract functions. These functions eagerly process every W3C baggage property, causing excessive memory allocations and retained memory disproportionate to the input size. This can lead to increased allocation and garbage collection pressure. Exploitation requires attacker-controlled input reaching baggage extraction before authentication or on a public route. The issue is fixed in version 1.47.0.
A vulnerability in OpenTelemetry-Go SDK versions from 1.33.0 up to 1.47.0 causes improper counting of valid U+FFFD replacement characters in attribute truncation logic. This defect allows attacker-controlled telemetry attributes to exceed configured memory and character limits, increasing memory usage and pipeline pressure. The issue does not affect confidentiality or integrity and is fixed in version 1.47.0.
In FRRouting (FRR) 8.3 through 10.5.1, bgp_notify_decapsulate_hard_reset() in bgpd/bgp_packet.c does not validate the length of the data field of a received BGP NOTIFICATION Cease/Hard Reset message (RFC 8538). When the data field is exactly one byte long, the function reads one byte past the end of a heap buffer and the 16-bit length of the encapsulated data underflows to 65535, causing a 65535-byte out-of-bounds heap read followed by an assertion failure. A remote BGP peer that has established a session and negotiated the Graceful Restart capability with the Notification (N) bit can send such a message to crash the bgpd daemon, terminating all BGP sessions (denial of service). This is fixed in 10.0.5, 10.1.5, 10.2.6, 10.3.4, 10.4.3, 10.5.2 and 10.6.0.
bit-vec is a compact vector of bits. Prior to version 0.10.0, there is undefined behavior if a user performs deserialize from an untrusted source and unsafe get_unchecked. A user of this library may be impacted by incorrect behavior if they perform deserialize from an untrusted source and run operations on the deserialized BitVec. This issue has been patched in version 0.10.0.
sqlite3 provides Ruby bindings for the SQLite3 embedded database. Prior to 2.10.2, sqlite3-ruby casts Ruby string lengths to int before passing SQL through Database#prepare, bound String or Blob values through Statement#bind_param, and String or Blob results from Ruby-defined SQL functions and aggregates through Database#create_function and Database#create_aggregate. On 64-bit platforms, a string of 4 GiB (2^32 bytes) or larger can wrap the length so SQLite processes only a prefix. A truncated SQL string can drop trailing clauses such as a WHERE condition, while a truncated bound value matters only when the application validated the full value before binding it. Exploitation requires the application and server to accept and retain the unusually large attacker-controlled string. If a dropped SQL clause contained a bind placeholder, binding raises SQLite3::RangeException instead of running the query. This issue is fixed in version 2.10.2.
Omnispace Agora Project versions up to 26.10.0 have a broken access control vulnerability in the isAutor() function. This function grants access rights based solely on object authorship without verifying if the user still belongs to the object's space. As a result, former members who authored objects can retain unauthorized read access after removal, causing persistent information disclosure.
Keep versions 0.34.10 through 0.55.0 contain a blind SQL injection vulnerability in the CEL-to-SQL converter. This flaw allows authenticated users with read:alert permission to craft CEL expressions that exploit unescaped bracket-indexed JSON keys in JSON path expressions for SQLite, PostgreSQL, and MySQL. Exploitation can lead to unauthorized extraction of other tenants' alerts and password hashes by using result counts as a boolean oracle.
Omnispace Agora Project versions through 26.10.0 have a SQL injection vulnerability that allows authenticated general administrators to inject arbitrary SQL via the personsSort session value. This value is used unsanitized in ORDER BY clauses in MdlUser.php and MdlSpace.php. Exploitation can leak database information such as the MariaDB version through error-based payloads on user and space listing pages.
Omnispace Agora Project versions through 26.10.0 have a vulnerability in token generation where the shared-calendar iCal share token can be predicted and forged by unauthenticated attackers. This is due to the token being derived from predictable fields such as object creation time, which is disclosed in the calendar metadata. Exploiting this allows unauthorized reading of shared calendar iCal feeds.
Omnispace Agora Project versions through 26.10.0 have an open redirect vulnerability in the Ctrl.php redir() function. This flaw allows remote attackers to manipulate the objUrl parameter to redirect users to arbitrary external URLs. Such redirects can be exploited for phishing attacks and credential theft by tricking users into visiting malicious sites.
Omnispace Agora Project versions through 26.10.0 have a vulnerability in token generation where the md5Id token can be predicted due to a missing dateCrea value. This allows unauthenticated attackers to compute valid tokens and access private calendar events by exploiting the misc&action=DisplayIcal endpoint without authentication.
Omnispace Agora Project versions through 26.10.0 have an insecure direct object reference (IDOR) vulnerability. Authenticated attackers can exploit this flaw by manipulating the reloadMailTypeId parameter in the CtrlMail.php component to access private mail messages of other users without proper ownership checks. This leads to unauthorized disclosure of sensitive communication content.
Omnispace Agora Project versions through 26.10.0 have a cross-site request forgery (CSRF) vulnerability. This flaw allows remote attackers to perform privileged actions, such as creating administrator users, by exploiting the merging of $_GET and $_POST parameters without requiring an anti-CSRF token. The vulnerability leverages the absence of CSRF protection combined with SameSite=Lax cookie behavior on top-level navigations, enabling attackers to craft malicious links or auto-navigating pages that issue GET requests to execute unauthorized actions.
Omnispace Agora Project versions through 26.10.0 are affected by a stored cross-site scripting (XSS) vulnerability. This flaw allows attackers to inject malicious HTML markup via imported directory data or uploaded CSV files. The vulnerability arises because input values are only UTF-8 encoded without proper HTML escaping, enabling crafted CSV cells to execute arbitrary scripts in the administrator's browser during import.
SQLBot versions through 1.10.3 use unsalted MD5 hashing for storing local account passwords in the sys_user.password field. This weak hashing method allows attackers who access the user table to recover passwords, including administrator credentials, via precomputed hash tables or GPU-accelerated cracking. The vulnerability arises from the use of md5pwd() in security.py, which does not apply salting to the hashes.
A critical OS command injection vulnerability exists in the TFTP provisioning module of Zenitel EdgeAudioClient versions before 9.6.3.0 and 10.x before 10.1.3.0. This flaw allows unauthenticated adjacent attackers to execute arbitrary commands as root by supplying a crafted DHCP option 66 value via a rogue DHCP server on the same network segment. The vulnerability affects devices using DHCP on every boot and lease renewal. Additionally, the injection can be triggered through certain configuration fields if an attacker can modify the device configuration.
A path traversal vulnerability exists in the certificate upload endpoint (/api/certificate/upload) of the turbineweb web interface in certain Zenitel devices running software versions from 10.0.3.0 up to but not including 10.1.3.0. Authenticated administrators can exploit this flaw by providing a crafted filename parameter with the type field set to any value other than https_certificate, bypassing path and certificate content validation. This allows arbitrary file write as root, which can lead to root-level arbitrary code execution by overwriting startup scripts or planting SSH keys.