CVE Vulnerability Catalog

In node-forge prior to 1.4.1, certificate.verify(child) selected RSA padding and RSASSA-PSS parameters from the issuer certificate rather than the child certificate. A child labeled RSASSA-PSS could be accepted with a PKCS#1 v1.5 signature when the issuer used PKCS#1 v1.5.

In glob from 9.0.0 until 14.0.2, abort branches in src/walker.ts, including GlobUtil.walkCB(), GlobUtil.walkCB2(), GlobUtil.walkCBSync(), and GlobUtil.walkCB2Sync(), invoke callbacks without returning. After AbortSignal or AbortSignal.timeout() rejects or emits an error, execution can continue into processor.processPatterns(), readdirCB(), and recursive traversal. The issue affects glob() and globStream() when applications expose attacker-influenced patterns or directory trees and rely on cancellation as a traversal budget.

In joi from 17.1.1 until 17.13.9 and 18.3.1, the Joi.string().email({ multiple: true }) rule uses a separator regular expression whose leading whitespace quantifier is retried at every position in a long whitespace run that contains no separator, causing quadratic work during String.prototype.split. This applies to the default separator and every custom separator. Applications that validate attacker-controlled values with the multiple option and no effective prior length limit can have the Node.js event loop blocked for seconds by one request.

ServiceNow remediated an information disclosure vulnerability in the ServiceNow AI Platform that could cause a user's plaintext password to be persisted in a system table. The password could potentially be exposed to a user who otherwise would not be entitled to view it. ServiceNow is not currently aware of malicious exploitation against ServiceNow instances.

ServiceNow remediated a sandbox escape vulnerability in the ServiceNow AI Platform. An authenticated user with the admin role could bypass Rhino sandbox restrictions and execute arbitrary code on the underlying host operating system.

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. No vulnerability information is available.

OpenBMB XAgent v1.0.0 contains a directory traversal vulnerability in main-upload_file-the-preserved-live-upload-file-witness-directly-reaches (ToolServer/ToolServerNode/main.py:46). This may allow access to files outside the intended directory.

TransformerOptimus SuperAGI v0.0.14 is vulnerable to incorrect access control in get_agent_execution_configuration in superagi/controllers/agent_execution_config.py. A remote authenticated attacker from one organization can read another organization's agent execution configuration by supplying the victim's agent_id and agent_execution_id to /agent_executions_configs/details/agent_id/{agent_id}/agent_execution_id/{agent_execution_id}. The endpoint lacks an organization ownership check on the selected agent and execution.

SuperAGI v0.0.14 contains an improper access control vulnerability in get_agent_by_latest_execution in superagi/controllers/agent_execution.py. A remote authenticated attacker from one organization can retrieve the latest execution and agent metadata for another organization's project through /agentexecutions/get/latest/agent/project/{project_id} by supplying a victim project_id.

SuperAGI up to v0.0.14 contains an improper access control vulnerability. The agent controller endpoint /api/agents/get/project/{project_id} allows authenticated users from one organization to retrieve the complete list of agents belonging to a different organization's project. The endpoint accepts a project_id parameter but does not verify that the project belongs to the authenticated user's organization.

DB-GPT v0.7.5 and 0.8.0 contains directory traversal in use_example_file (packages/dbgpt-app/src/dbgpt_app/openapi/api_v1/examples_api.py:129). A remote attacker can use the validated exploitation path to write files outside the intended workspace or storage boundary.

modelscope agent-zero 1.7, 1.8, 1.9, and 1.10 is vulnerable to Directory Traversal in python/helpers/file_browser.py:FileBrowser.save_text_file. The save_text_file method accepts user-controlled file paths without normalization or validation, allowing path traversal attacks.

In the Botan C++ cryptography library, the C API function botan_block_cipher_block_size converted a size_t block size to int without a bounds check. In an application that accepts external algorithm parameter strings and uses FFI raw ECB mode, an attacker can select the variable-block-size Lion cipher, causing the reported size to be truncated, insufficient memory allocation, and later memory corruption. The issue is fixed in version 3.13.0.

In the Botan library, the botan ocsp_check command requested an OCSP response from a certificate's Authority Information Access URL without verifying the response signature or authorizing the signer. A malicious responder or on-path attacker could return a matching and timely GOOD response with an empty, invalid, or unauthorized signature, causing a revoked certificate to produce exit status 0 and OCSP check OK output. Only the command-line interface is affected; the issue is fixed in version 3.13.0.

In the Botan library, the Python binding converted Python strings containing U+0000 to const char* values without consistently rejecting the embedded NUL, causing bcrypt and check_bcrypt to process only the prefix before the NUL. Applications could validate a longer password but hash a shorter effective value, allowing application password-policy bypass; scrypt and argon2 are unaffected. The issue is fixed in version 3.13.0.

In the Botan library, the online OCSP client prior to 3.13.0 allowed a single HTTP redirect while posting an OCSP request to the URI in a certificate's Authority Information Access extension. A malicious OCSP responder or on-path attacker could redirect the client to make one blind request to an otherwise unreachable internal HTTP service, resulting in blind SSRF; response timing can provide a coarse internal-service oracle. The issue is fixed in version 3.13.0.

The socket.getaddrinfo() function accepted null bytes within the *host* and *port* parameters, which could cause the values to be silently truncated. This may lead to unintended name resolution or connections to a different address than intended.

HashiCorp Nomad and Nomad Enterprise are vulnerable to symlink following during dispatch payload and executor log writes. A malicious workload may modify files outside its allocation directory.

HashiCorp Nomad and Nomad Enterprise are vulnerable to cross-namespace authorization bypasses in several read-only API endpoints. An authenticated user with read permissions in one namespace may view information about objects in other namespaces. This is fixed in Nomad Community Edition 2.1.1 and Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.

In @sd-jwt/decode (also used by @sd-jwt/core) version 0.19.0 and earlier, a tampered Disclosure whose digest no longer matches the Issuer-signed _sd array is silently dropped, returning a reduced claim set and reporting success. This affects both tampered Disclosures that remain valid JSON and those containing invalid UTF-8 bytes, which are substituted with U+FFFD replacement characters. It violates RFC 9901 section 7.1 step 5 and step 3 / section 4.2.1, which require rejection of unreferenced and invalid Disclosures.