Kartones flask-calendar before commit bfde72e contains a stored cross-site scripting vulnerability because task_details_for_markup returns unescaped content rendered with the |safe filter. Authenticated shared calendar members can store script in task details that executes for other members, letting attackers read and modify their private calendars.
In `github.com/eclipse-keypont/crypto11/v2` versions `<= 2.0.0-rc8` (and the deprecated v1 module paths `github.com/eclipse-keypont/crypto11 <= 1.6.8`, `github.com/ThalesGroup/crypto11 <= 1.7.0-rc1` and `github.com/ThalesIgnite/crypto11 <= 1.2.5`), the `cipher.AEAD` returned by `SecretKey.NewGCM()` passes whatever nonce it is given straight to `CK_GCM_PARAMS` without checking its length against `NonceSize()`, and accepts an empty nonce. On a token that accepts a zero-length GCM IV — SoftHSM2 does — every `Seal` with an empty nonce encrypts under the same IV, reusing the keystream and exposing the GHASH authentication key, which allows forgeries. Separately, `Config.UseGCMIVFromHSM` sends a NULL IV with length zero to the token unless `GCMIVFromHSMControl.SupplyIvForHSMGCMEncrypt` is also set, so the token has nowhere to write the IV it generates: a `Seal` with a non-empty nonce panics after the plaintext has already been encrypted, and a `Seal` with an empty nonce returns ciphertext under an empty IV without error. On the v1 line HSM-IV mode additionally never copies the token-generated IV back to the caller, so the caller keeps its own nonce while the data was encrypted under another one.
Incomplete validation of external ad-reply URLs in WhatsApp for Android and WhatsApp Business for Android before 2.26.17.4 could have caused a target's device to reveal its IP information to an attacker if an attacker sent media from an attacker-controlled URL when a crafted Click to WhatsApp ad-reply message was rendered and displayed in a message thread. This issue may have been abused in conjunction with specific spam messages.
Improper following of a certificate’s chain of trust in the remote-attestation verifier used to establish trust with Meta AI's confidential computing backend in WhatsApp for iOS before 2.26.24.72, WhatsApp Business for iOS and WhatsApp for Mac Desktop before v2.26.23.72, WhatsApp for Android before v2.26.23.74, and WhatsApp Business for Android before v2.26.23.70 could have allowed someone positioned within Meta infrastructure to bypass the hardware root of trust by presenting clients with a VCEK certificate signed by a key other than the hardware manufacturer’s. Any such VCEK Cert would first have to be published to the third-party binary transparency ledger used by WhatsApp Private Processing. The ledger shows that every published VCEK certificate chains to the hardware root of trust, confirming no exploitation.
A SQL injection vulnerability when the recipient tapped on a specially crafted “order details” message from an unofficial client in WhatsApp for Android prior to version 2.26.35.74 could have allowed deletion of locally-stored WhatsApp files and, only if the user is online at time of receipt, leaked one bit of information asked by the attacker about the user’s chat database via an induced-crash delivery receipt timing sidechannel. We have not seen evidence of exploitation in the wild.
A critical security update for the Eclipse Temurin build of OpenJDK 25 (version 25.0.5.1) for Windows addresses multiple vulnerabilities including memory corruption, Kerberos ticket handling, TLS connection improvements, and other Java runtime enhancements. This update replaces version 25.0.5 and includes fixes for ten CVEs related to security and bug issues in the Java Development Kit (JDK).
flowintel prior to version 4.1.0 contains an information disclosure vulnerability in its case history feature. Authenticated users with access to a case can view references to other cases in the history output without proper permission checks, exposing identifiers and titles of cases they should not access. This affects multiple output methods including browser views, API endpoints, and report generation.
flowintel versions prior to 4.1.0 contain a vulnerability in the case and task classification usage endpoints that allows authenticated users to access classification data for cases they are not authorized to view. The endpoints do not enforce proper object-level access controls, enabling enumeration of classification usage across all cases, including private or restricted ones. This could expose sensitive information about case existence and associated threat data.
FlowIntel's alerting module had an authorization bypass vulnerability in its alert access control logic prior to version 4.1.0. The system incorrectly relied only on connector ownership to grant access to alerts linked to private cases, without verifying if the user was still a valid member of the private case. This allowed unauthorized users to view sensitive alert details and modify alert statuses or create cases from alerts they should not access. Additionally, a time-of-check to time-of-use (TOCTOU) race condition could expose private case identifiers to unauthorized users during concurrent operations.
FlowIntel's chatbot component prior to version 4.1.0 used a single shared Model Context Protocol (MCP) session and a process-wide environment variable to handle per-user API credentials. This design flaw allowed credentials from one user to be accessible or applied to another user's chatbot tool invocation, leading to potential unauthorized data access. The vulnerability could cause lower-privilege users to access higher-privilege user data and allow invalidated sessions to continue operating under cached credentials.
flowintel, a case management application, has a logic flaw in task creation that allows tasks in privileged cases to bypass the required approval workflow. Specifically, tasks can be initialized with a Created status instead of the required Requested status in two scenarios involving templates. This flaw enables authenticated users with task or case creation privileges to activate tasks directly in privileged cases without supervisory approval, potentially exposing restricted content or unauthorized actions. The issue affects flowintel versions prior to 4.1.0.
flowintel versions prior to 4.1.0 have an authorization flaw in the recurring reminder notification subsystem. Users who previously had access to private cases but later lost access can still receive and view recurring reminder notifications related to those cases. This flaw allows unauthorized information disclosure of case titles, reminder messages, and metadata. There is no impact on data integrity or availability.
A vulnerability in the flowintel application's calendar functionality allowed unauthorized users to access private case data. The calendar queries did not enforce visibility checks on parent cases, exposing tasks assigned to users or their organizations without verifying permission. This led to potential information disclosure of private cases. The issue affected task visibility logic and assigned-only task queries. A fix has been implemented to recheck case visibility alongside task assignment and organization membership, preventing unauthorized data exposure. The vulnerability affects flowintel versions prior to 4.1.0.
flowintel prior to version 4.1.0 contains an authorization flaw in its user deletion functionality. Organization-scoped administrators can delete platform-level administrator accounts within their organization, bypassing intended privilege hierarchies. This flaw allows deletion of higher-privilege accounts by lower-privilege org admins, leading to loss of administrative oversight and potential disruption of platform management.
flowintel versions prior to 4.1.0 contain an authorization bypass vulnerability in the browser-based admin user editing interface. This flaw allows an authenticated organization-admin user to modify platform-admin accounts, including changing credentials and roles, due to inconsistent authorization checks between the admin panel and API layer.
FlowIntel prior to version 4.1.0 contains an authorization bypass vulnerability in its task management workflow. This flaw allows users with only basic task-level permissions to revive completed privileged cases by reopening tasks or creating new tasks within those cases. The system fails to enforce the required Admin or Case Admin privilege checks before reviving a case, potentially disrupting case lifecycle management and exposing cases to unauthorized modifications.
flowintel versions prior to 4.1.0 have a vulnerability in the MISP correlation feature that allows authenticated users to access case identifiers they are not authorized to see. The flaw arises from missing access control checks when generating correlation lists for MISP attributes, enabling unauthorized disclosure of case existence information.
FlowIntel versions prior to 4.1.0 have an information disclosure vulnerability in the case serialization logic. Authenticated users with read access to a case could receive connector metadata belonging to other users or organizations, including URLs, descriptions, UUIDs, and potentially API credentials. This exposure crosses organizational boundaries and leaks sensitive connector infrastructure details.
flowintel versions prior to 4.1.0 contain an authorization bypass vulnerability in the file-to-note conversion feature for case tasks. This flaw allows authenticated users with basic case membership roles (such as editor or queuer) to perform conversion actions on tasks in restricted workflow states (Requested, Rejected, or Request Review) without the required elevated roles. This bypass enables unauthorized reading of attached file contents and creation of notes on restricted tasks, potentially disrupting workflow and circumventing access controls.