Xlabaiteam

**Name of the Vulnerable Software and Affected Versions** MindsDB versions prior to 25.9.1.1 **Description** MindsDB, a platform for building artificial intelligence from enterprise data, has a path traversal flaw in its /api/files interface. An authenticated attacker can exploit this to achieve remote command execution. The vulnerability resides in the "Upload File" module, specifically at the /api/files API endpoint. The system does not perform security checks on uploaded file paths, allowing attackers to use `../` sequences in the filename to perform path traversal. The file write operation occurs before filename filtering, enabling arbitrary content to be written to any location on the server. An attacker can overwrite existing executable files, potentially achieving Remote Code Execution (RCE) by overwriting files like `/venv/lib/python3.10/site-packages/pip/ init .py` and triggering their execution through other MindsDB functionality, such as handler installation. **Recommendations** Upgrade to MindsDB version 25.9.1.1 or later to resolve this vulnerability.

**Name of the Vulnerable Software and Affected Versions** cryptography versions prior to 46.0.5 **Description** The `public key from numbers` (or `EllipticCurvePublicNumbers.public key()`), `EllipticCurvePublicNumbers.public key()`, `load der public key()`, and `load pem public key()` functions do not validate that the provided public key point belongs to the expected prime-order subgroup of the curve. This missing validation allows an attacker to supply a public key point `P` from a small-order subgroup, potentially leading to security issues in signature verification (ECDSA) and shared key negotiation (ECDH). When using ECDH, the victim's private key modulo the small subgroup order may be leaked. For curves with a cofactor greater than 1, the least significant bits of the private key are revealed. Exploiting this issue with weak public keys in ECDSA enables signature forgery on the small subgroup. This issue only impacts SECT curves. **Recommendations** Upgrade to cryptography version 46.0.5 or later.

**Name of the Vulnerable Software and Affected Versions** Alist versions prior to 3.57.0 **Description** Alist is a file list program that supports multiple storages, powered by Gin and Solidjs. The application contains a path traversal issue in multiple file operation handlers. An authenticated attacker can bypass directory-level authorization by injecting traversal sequences into filename components. This allows unauthorized file removal, movement, and copying across user boundaries within the same storage mount. The vulnerability affects file operations and potentially compromises data integrity and confidentiality. **Recommendations** Update to version 3.57.0 or later.

**Name of the Vulnerable Software and Affected Versions** Alist versions prior to 3.57.0 **Description** Alist, a file list program powered by Gin and Solidjs, has a configuration issue where TLS certificate verification is disabled by default for all outgoing storage driver communications. This allows for potential Man-in-the-Middle (MitM) attacks, enabling decryption, theft, and manipulation of data transmitted during storage operations. This compromises the confidentiality and integrity of user data. **Recommendations** Update to version 3.57.0 or later.

**Name of the Vulnerable Software and Affected Versions** OpenList Frontend versions prior to 4.1.10 **Description** The OpenList Frontend application contains a path traversal flaw in multiple file operation handlers within the `server/handles/fsmanage.go` file. The application directly concatenates filename components from the `req.Names` variable with validated directories using `stdpath.Join`, allowing attackers to bypass path restrictions using ".." sequences. This enables authenticated attackers to access files belonging to other users within the same storage mount and perform unauthorized actions, including deletion, renaming, and copying. The vulnerable functions include `FsRemove` and `FsCopy`. An attacker can exploit this by injecting traversal sequences into filename components. The vulnerability allows privilege escalation within shared storage environments. **Recommendations** Versions prior to 4.1.10: Upgrade to version 4.1.10 or later to resolve this issue.

**Name of the Vulnerable Software and Affected Versions** OpenList versions prior to 4.1.10 **Description** The OpenList application disables TLS certificate verification by default for all outgoing storage driver communications, creating a risk of Man-in-the-Middle (MitM) attacks. This allows attackers to intercept and manipulate all storage communications, potentially leading to the decryption, theft, and manipulation of data. Attackers can leverage network-level attacks, such as ARP spoofing or compromised network equipment, to redirect traffic to malicious endpoints. The `TlsInsecureSkipVerify` setting is set to true by default in the `DefaultConfig()` function. This enables attackers to establish encrypted connections with attacker-controlled servers, allowing full decryption and manipulation of storage operations without security warnings. A proof-of-concept demonstrated successful interception of authentication cookies by redirecting traffic to a malicious HTTPS server. **Recommendations** Versions prior to 4.1.10: Upgrade to version 4.1.10 or later to enable certificate verification and mitigate the risk of MitM attacks.

**Name of the Vulnerable Software and Affected Versions** sm-crypto versions prior to 0.3.14 **Description** sm-crypto, a JavaScript library providing implementations of Chinese cryptographic algorithms SM2, SM3, and SM4, contains a flaw in the SM2 decryption logic. An attacker can recover the private key by repeatedly interacting with the SM2 decryption interface, requiring approximately several hundred interactions. This issue could compromise confidentiality. **Recommendations** Versions prior to 0.3.14 should be updated to version 0.3.14 or later.

**Name of the Vulnerable Software and Affected Versions** sm-crypto versions prior to 0.4.0 **Description** sm-crypto provides JavaScript implementations of Chinese cryptographic algorithms SM2, SM3, and SM4. A flaw exists in the SM2 signature verification logic that allows an attacker to forge valid signatures for arbitrary public keys under default configurations. If the message space has sufficient redundancy, the attacker can adjust the message prefix to meet specific formatting needs. **Recommendations** Update to version 0.4.0 or later.

**Name of the Vulnerable Software and Affected Versions** sm-crypto versions prior to 0.3.14 **Description** The sm-crypto library, providing JavaScript implementations of Chinese cryptographic algorithms SM2, SM3, and SM4, contains a signature malleability issue in its SM2 signature verification logic. An attacker can generate a new valid signature for a previously signed message using an existing signature. **Recommendations** Update to version 0.3.14 or later.

**Name of the Vulnerable Software and Affected Versions** RustCrypto versions 0.14.0-pre.0 through 0.14.0-rc.0 **Description** The RustCrypto Elliptic Curves library provides Elliptic Curve Cryptography (ECC) support. A denial-of-service issue exists in the SM2 public-key encryption implementation where unchecked slice operations on input buffers derived from ciphertext can lead to bounds-check panics, potentially crashing the calling thread or process. An attacker can exploit this by submitting short or crafted ciphertext. **Recommendations** Update to a version beyond 0.14.0-rc.0.

**Name of the Vulnerable Software and Affected Versions** RustCrypto versions 0.14.0-pre.0 through 0.14.0-rc.0 **Description** The RustCrypto Elliptic Curves library provides general purpose Elliptic Curve Cryptography (ECC) support. A denial-of-service issue exists in the SM2 PKE decryption path where an invalid elliptic-curve point (C1) is decoded and the resulting value is unwrapped without validation. Specifically, `AffinePoint::from encoded point(&encoded c1)` may return a `None` value when the supplied coordinates are syntactically valid but do not lie on the SM2 curve, leading to a panic due to the use of `.unwrap()`. **Recommendations** Update to a version past 0.14.0-rc.0.

**Name of the Vulnerable Software and Affected Versions** RustCrypto versions 0.14.0-pre.0 through 0.14.0-rc.0 **Description** The Elliptic Curves library within RustCrypto, a general-purpose Elliptic Curve Cryptography (ECC) implementation, contains a flaw in its SM2 Public Key Encryption (PKE) implementation. The issue stems from reduced entropy during ephemeral nonce (k) generation, caused by a unit mismatch error requesting only 32 bits of randomness instead of the expected 256 bits. This significantly weakens the encryption, reducing its security from 128 bits to 16 bits, potentially allowing an attacker to recover the nonce and decrypt ciphertext given the public key and ciphertext. **Recommendations** Versions prior to 0.14.0-pre.0 and after 0.14.0-rc.0 should be used.

**Name of the Vulnerable Software and Affected Versions** Flowise versions prior to 3.0.8 **Description** Flowise is a drag and drop user interface used to build customized large language model flows. Versions prior to 3.0.8 contain a flaw in the `WriteFileTool` and `ReadFileTool` components where file path access is not restricted. This allows authenticated attackers to read and write arbitrary files to any path in the file system, potentially leading to remote command execution. Approximately 12.7k potential targets have been identified. The issue involves unrestricted file path access within the `ReadFileTool` and `WriteFileTool` components, enabling attackers to pivot from file access. **Recommendations** Update Flowise to version 3.0.8 or later.

Name of the Vulnerable Software and Affected Versions: gnark versions prior to 0.14.0 Description: gnark is a zero-knowledge proof system framework. The `Verify` function in `eddsa.go` and `ecdsa.go` used the `S` value from a signature without asserting that 0 ≤ `S` < order, leading to a signature malleability issue. This is due to a lack of essential constraints in gnark’s native EdDSA and ECDSA circuits, allowing multiple distinct witnesses to satisfy the same public inputs. In protocols where nullifiers or anti-replay checks are derived from `R` and `S`, this enables signature malleability and may allow double spending. Recommendations: Update to version 0.14.0 to resolve this issue.