CVE Vulnerability Catalog

A privilege escalation vulnerability in the ClearPass Policy Manager OnGuard Linux agent could allow malicious users to escalate to root privileges on the affected Linux client.

A command injection vulnerability in the API of ClearPass Policy Manager allows an authenticated remote attacker to escalate privileges and gain administrative control of the system.

A command injection vulnerability in the client software of ClearPass Policy Manager allows an attacker supplying crafted input to execute arbitrary commands with elevated privileges on the affected host.

An authenticated path traversal vulnerability in the command line interface of ClearPass Policy Manager allows a low-privileged authenticated remote attacker to execute arbitrary code with elevated privileges on the underlying OS.

A vulnerability in the web-based management interface of ClearPass Policy Manager allows an unauthenticated remote attacker to conduct a stored XSS attack against an administrative user, enabling arbitrary script execution in the victim's browser.

An improper access control vulnerability in the Android client application for HPE Networking ClearPass Policy Manager allows an unauthenticated remote attacker, with user interaction, to obtain sensitive information from the affected user.

A privilege escalation vulnerability in the API of AOS-S allows an authenticated read-only user to escalate privileges and gain administrative access to the system.

Gitea validates a repository migration hostname against its network allow and block lists before invoking Git, but the Git subprocess independently resolves the hostname when connecting. An attacker who can start a migration and control the destination's DNS can change the address between validation and connection to reach a blocked internal address. The affected path is the Git clone operation; validation in the migration HTTP client's dialer does not protect the independently connecting Git subprocess.

The yawkat LZ4 Java library versions 1.7.0 through 1.11.4 contain a vulnerability in the insecure creation of a temporary file. An attacker with access to a shared temporary directory can replace the native library file before it is loaded, potentially leading to code execution in the victim's context.

The StableLib library before version 2.0.4 contains a vulnerability in the CBOR decoder that allows an attacker to inject a '__proto__' key into a JavaScript object. This overwrites the object's prototype, potentially leading to security decisions based on attacker-controlled data.

The StableLib library before version 2.0.4 contains a vulnerability in the CBOR decoder that does not enforce a maximum nesting depth. A sufficiently deep structure can cause a JavaScript stack overflow, leading to a crash of the process or service.

Gitea validated the initial remote URL for push mirrors, wiki remote checks, and fetches of migrated pull request heads, but the subsequent raw Git operations followed HTTP redirects without revalidating the destination. A repository administrator using a policy-allowed endpoint that redirects could make Gitea's Git client send requests to an address that the outbound host policy would otherwise block. The impact depends on the configured policy and the internal services reachable from the server.

Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with Actions write access cancelled a run that was awaiting approval and then re-ran it, the new jobs were created as waiting rather than blocked while the run still recorded that approval was required. Cancelling and re-running stale fork checks is a routine action that does not involve the approval control, so where Actions is enabled and a matching runner is registered, workflow code taken from the fork pull request head could run on the repository's runners without an explicit approval.

A user who can open a fork pull request can place workflow content with a shared run-level concurrency group into a Gitea Actions run that is awaiting approval. When a later run in that group cancels the blocked job, the run becomes terminal while still marked as needing approval. If a maintainer later approves the run, Gitea passed the already-cancelled job back through concurrency preparation, set it to waiting, and made it claimable by a matching runner, executing fork-controlled workflow code. Exploitation requires the maintainer's later approval action, Actions to be enabled, and a runner that accepts the repository's jobs.

When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could cancel trusted in-progress runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.

Changing an organization team's permission through the API with only the `permission` field did not rebuild the team's per-unit access, and the requested level was not applied as a cap. After an organization owner demoted a team, for example from admin to read, the team's members kept their previous unit permissions, including write access to the team's repositories. The web form was not affected.

Elasticsearch contains an authorization bypass vulnerability in the Remote Cluster Security (RCS) 2.0 model. An attacker with a valid API key can send a specially crafted cross-cluster search request that is authorized for one index but actually operates on a different, unauthorized index, exposing its data.

Elasticsearch contains an incorrect authorization vulnerability in a configurable, non-default privilege that allows an administrator to delegate limited role-management capability. Due to incomplete enforcement of scope, a user with this privilege can expand their access to indices that should remain restricted, including internal security data.

Kibana contains an authorization bypass vulnerability in the Fleet package installation process. A user with delegated Fleet package-management privileges can claim a data stream identifier already in use by another tenant, redirecting the victim's data to infrastructure controlled by the attacker.

Arista Wi-Fi access points contain a memory corruption vulnerability in the wired uplink network endpoints. An unauthenticated attacker on the same network segment can crash the sensor service or potentially achieve remote code execution.