CVE Vulnerability Catalog

Vulnerability in knowns versions before 0.30.0 contain a path traversal vulnerability in the handleCodeReplace() function that allows attackers to overwrite arbitrary files outside the project root. Attackers can supply absolute paths or relative paths containing directory traversal sequences to write malicious content to sensitive files like shell startup scripts or SSH configuration files.

Vulnerability in knowns versions before 0.30.0 fail to validate the settings.lsp.languages binary field in project configuration files, allowing attackers to execute arbitrary binaries by crafting a malicious .knowns/config.json file. When a repository with a crafted configuration is opened, the unvalidated binary path is executed twice under the user's account without any verification.

Vulnerability in knowns through 0.33.0 contains a server-side request forgery vulnerability in the POST /api/embedding-models/test endpoint that issues outbound requests to caller-supplied destinations without validation. Attackers can enumerate internal hosts and cloud metadata endpoints by observing transport error messages that reveal network reachability information.

Vulnerability in knowns versions before 0.30.0 contain a path traversal vulnerability in the POST /api/templates/preview endpoint that allows unauthenticated attackers to read arbitrary files. Attackers can supply directory traversal sequences in the templateFile parameter to bypass path restrictions and read sensitive files like credentials and configuration through the JSON response.

Vulnerability in knowns versions before 0.30.0 fail to validate filesystem paths in MCP tool arguments, allowing attackers to read, create, overwrite and delete files outside the project directory. Attackers can supply path arguments containing directory traversal sequences to access arbitrary Markdown files accessible to the server process.

Vulnerability in ash_authentication_oauth2_server allows an unauthenticated attacker to register OAuth clients even when Dynamic Client Registration is gated by an initial access token. The resolve_secret/3 function treats any return other than {:ok, _} or :error as a valid secret, allowing bypass of protections.

SSRF vulnerability in ash_authentication_oauth2_server allows an attacker who controls a client metadata URL and its DNS to make the server connect to internal or loopback addresses. The public_ip?/1 function incorrectly classifies certain address ranges as public, allowing policy bypass.

Vulnerability in ash_authentication_oauth2_server allows an unauthenticated attacker to inject arbitrary authentication parameters into the WWW-Authenticate challenge header. The resource_metadata value is interpolated without proper escaping, allowing header modification and redirecting clients to a malicious authorization server.

Vulnerability in ash_authentication_oauth2_server allows a shared HTTP cache to serve one tenant's OAuth discovery metadata to another tenant's clients. Responses with metadata are marked as Cache-Control: public without a Vary header, causing responses to be cached and served to other tenants.

Vulnerability in ash_authentication_oauth2_server exposes state-changing OAuth endpoints under an unintended URL prefix, bypassing controls scoped to the canonical prefix. Routes are mounted under both /oauth and /.well-known, allowing access to /register, /token, and /revoke via alternative paths.

Resource exhaustion vulnerability in ash_authentication_oauth2_server. An unauthenticated attacker can exhaust database storage and memory by sending requests to the /authorize endpoint with many distinct client_id URLs, creating permanent client rows and caching documents without limits.

Vulnerability in ash_lua allows user-supplied Lua scripts to read attributes not on the exposed-field allow-list. The read action's aggregate path does not consult the allow-list, enabling access to sensitive data such as passwords.

A vulnerability in the igniter library of the ash-project allows a malicious package publisher to forge the mix igniter.install confirmation prompt. The metadata fields are not properly neutralized, allowing ANSI escape sequences to overwrite the confirmation panel, hiding real information and presenting fake author names or download counts.

A vulnerability in ash_double_entry of the ash-project allows an attacker to submit several distinct string spellings of the same ULID identifier. Due to improper masking of the first character, multiple strings decode to the same value, enabling desynchronization of string-level checks such as idempotency keys or deny-lists.

Lara Dashboard before 1.3.2 fails to authorize the MarketplaceModuleBrowser installModule Livewire action, allowing non-Superadmin administrators to install modules. Attackers can download and auto-activate arbitrary PHP modules from the marketplace over unsigned HTTP requests, achieving remote code execution.

Lara Dashboard before 1.3.2 authorizes the POST /admin/settings/core-upgrades/upload endpoint with only the settings.edit permission, allowing non-Superadmin administrators to upload and extract arbitrary zip archives over the live application source code. Attackers can upload a malicious archive containing modified application files such as routes/web.php with embedded system commands, which execute as the web server user with access to environment secrets and database credentials.

Lara Dashboard before 1.3.2 fails to authorize access to the post-builder image and video upload endpoints, allowing authenticated accounts without content permissions to upload files. Attackers can upload polyglot files with attacker-chosen extensions to the public web root and execute code if the deployment permits execution of the uploaded file type.

A vulnerability in the Net::IP::LPM module for Perl before version 1.12 accepts malformed prefix lengths. Invalid values are treated as 0 or truncated, poisoning the lookup table and causing lookups to always succeed, so an allow-list permits all addresses and a deny-list blocks all addresses.

A vulnerability in the Protocol::HTTP2 module for Perl before version 1.14 allows memory exhaustion via closed streams that are never removed from the connection stream table. Each closed stream leaves an entry, and stream identifiers increase monotonically, allowing an attacker to open and close streams indefinitely, leading to memory growth.