CVE Vulnerability Catalog

Missing queue-set type validation in xQueueAddToSet() in the FreeRTOS-Kernel before 11.3.1 might allow an unprivileged task on MPU-enabled ports with configUSE_QUEUE_SETS=1 to read privileged kernel memory. To remediate this issue, users should upgrade to version 11.3.1 or later.

FreeRTOS-Kernel before version 11.3.1 lacks minimum size validation in secure context allocation, which might allow local users to corrupt secure-world heap metadata via an out-of-bounds write with an undersized stack size parameter.

FreeRTOS-Kernel before version 11.3.1 lacks privilege verification in the secure context cleanup handler, which might allow local users to cause a use-after-free condition in secure-world memory via the SVC handler for secure context deallocation.

FreeRTOS-Kernel before version 11.3.1 has improper input validation, which might allow an unprivileged task on MPU-enabled ports to execute code in privileged kernel context.

Checkmate from version 3.3.0 until 3.9.2, when the global showURL setting is enabled, causes the unauthenticated GET /api/v1/status-page/:url endpoint to return complete monitor objects, including the secret field used as an HTTP Authorization credential, even though it is not displayed in the UI.

Infracost prior to 0.10.45, internal/hcl/remote_variables_loader.go and related Terraform Cloud, remote-plan, and Terragrunt registry request paths can attach a configured Terraform Cloud or registry token to a destination hostname derived from untrusted Terraform input without confirming that it is the configured trusted host. When a CI run provides a token while scanning attacker-controlled Terraform, including pull_request_target or a same-repository pull request, an attacker can direct the request to an attacker-controlled host and disclose the token. Standard fork pull_request workflows without secrets are not exposed.

Prior to version 0.10.45, Infracost had a vulnerability where the template functions readFile, pathExists, isDir, and matchPaths did not resolve intermediate directory symlinks. A repository could contain a path such as evil/file where evil points outside the checkout, causing os.ReadFile and related operations to follow the symlink and read runner-accessible files. The resulting content could be rendered into generated configuration and surfaced through the Infracost dashboard or pull request comment, with greater impact in workflows that provide repository secrets.

In Checkmate versions from 3.5.1 to 3.9.2, an authenticated admin or superadmin can set matchMethod to regex and place a malicious expression in the expectedValue field for advanced HTTP monitor matching. The expression is synchronously evaluated on the Node.js main event loop without a timeout or worker isolation, allowing catastrophic backtracking to freeze API endpoints, monitor checks, and WebSocket connections for all users. This issue is fixed in version 3.9.2.

Omnigent before version 0.3.0 allows an authenticated user to upload a session-scoped agent bundle with an absolute or traversal-containing os_env.cwd value because the parser stores the value verbatim and the validator does not constrain it. When OMNIGENT_RUNNER_WORKSPACE is unset, an attacker can control the path and gain access to runner files and environment secrets outside the intended workspace.

Omnigent before version 0.3.0 has a shared shell-command parser that fails to recognize combined interpreter flags, timeout, nice, setsid, and stdbuf wrappers, command substitutions, and a single background control operator. Commands hidden with these forms produce no parsed operation, causing allowlist and workspace confinement policies to abstain and allow the command.

Omnigent before version 0.3.0 accepts an agent bundle in multipart POST /v1/sessions, and the validator does not reject a dotted Python path in tools..callable. The dispatcher imports the specified module and invokes the function, allowing a bundle to select subprocess.check_output and execute a local command with the runner process permissions.

Omnigent is an open-source AI agent framework and meta-harness for orchestrating coding agents. Prior to 0.3.0, PUT /sessions/{session_id}/agent checks LEVEL_EDIT permission for a session but does not reject a bound shared or template agent whose agent.session_id is None. An authenticated user with edit access to a session can replace that shared agent bundle through omnigent/server/routes/sessions.py, add a stdio MCP server, and cause later sessions that use the shared agent to launch an attacker-controlled command through omnigent/tools/mcp.py. The command executes with the Omnigent runner process permissions and can expose files, credentials, workspace data, internal services, and runner availability. This issue is fixed in version 0.3.0.

Checkmate before version 3.9.1 has a memory exhaustion vulnerability in the public registration endpoint. An unauthenticated attacker can send multiple concurrent oversized files that are buffered before validation, leading to memory exhaustion and backend crash.

UAC before version 3.3.0 has a command injection vulnerability in the user substitution logic in parse_artifact.sh. Usernames and home directories from /etc/passwd are substituted into command strings without proper escaping before execution via eval, allowing injection of shell metacharacters.

UAC before version 3.3.0 has a command injection vulnerability in the _command_collector function, where foreach command output lines are substituted into command strings via sed without proper escaping before being evaluated with eval. Attackers can exploit malicious filenames or artifact definitions.

UAC before version 3.3.0 has a command injection vulnerability in the _run_command function that allows attackers to execute arbitrary commands by injecting shell metacharacters into untrusted data such as usernames, process names, or filenames.

In Johnson Controls Simplex Incident Manager / Autocall Fire Administrator before version 2.01.05, there is a vulnerability of cleartext storage of sensitive information in memory. An attacker may exploit this to retrieve embedded sensitive data.

TP-Link TL-MR6400 v7 router has a stack-based out-of-bounds write vulnerability in the login request handling of the administrative web interface. An unauthenticated adjacent attacker can send a specially crafted malformed HTTP request, causing the web service process to crash.

TP-Link TL-MR6400 v7 router has a NULL pointer dereference vulnerability in the HTTP request parsing functionality. An unauthenticated remote attacker can send a specially crafted HTTP request with a malformed session cookie header, causing the HTTP service process to crash.

TP-Link TL-MR6400 v7 router has a stack-based buffer overflow vulnerability in the firmware update functionality due to unsafe processing of attacker-controlled metadata within a firmware image. An authenticated attacker can exploit this to trigger memory corruption and execute arbitrary code.