Alvaro Muñoz

O problema decorre do parâmetro `role`, controlado pelo usuário, que é inserido no aplicativo no Kubernetes::RoleVerificationsController. Esse parâmetro é encaminhado para o inicializador RoleConfigFile e, em seguida, para o método Kubernetes::Util.parse file, onde é deserializado de forma insegura usando o método YAML.load stream. Isso pode levar à execução remota de código (RCE).

A cross-site request forgery (CSRF) vulnerability allows attackers to connect to an attacker-specified URL, capturing GitHub credentials associated with an attacker-specified job. This issue is due to an incomplete fix and results from not requiring POST requests for an HTTP endpoint. The vulnerability enables attackers to exploit the `HTTP endpoint` and capture sensitive information.

The issue is related to insufficient protection of registration data, allowing attackers with Item/Configure permission to access and capture credentials they are not entitled to. This is due to the plugin not setting the appropriate context for credentials lookup. Attackers can exploit this to gain unauthorized access to protected information.

A cross-site request forgery (CSRF) vulnerability allows attackers to trick users into logging in to the attacker's account. This issue arises because the plugin does not implement a state parameter in its OAuth flow, which is a unique and non-guessable value associated with each authentication request.

A cross-site request forgery (CSRF) vulnerability allows attackers to connect to an attacker-specified URL and to check for the existence of directories, `.csv`, and `.ycsb` files on the Jenkins controller file system. This issue arises because the plugin does not perform a permission check in a method implementing form validation, allowing attackers with Overall/Read permission to exploit this vulnerability. Furthermore, the form validation method does not require POST requests, contributing to the CSRF vulnerability.

A missing permission check in the plugin allows attackers with Overall/Read permission to connect to an attacker-specified URL. This issue also results in a cross-site request forgery (CSRF) vulnerability, as the form validation method does not require POST requests.

A cross-site request forgery (CSRF) vulnerability allows attackers to connect to an attacker-specified URL. The issue arises from a lack of permission check in a method implementing form validation, which can be exploited by attackers with Overall/Read permission. Furthermore, the form validation method does not require POST requests, contributing to the CSRF vulnerability.

A missing permission check in the plugin allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials, including `username` and `password`. This issue also results in a cross-site request forgery (CSRF) vulnerability, as the affected HTTP endpoint does not require POST requests.

A cross-site request forgery (CSRF) vulnerability allows attackers to connect to an attacker-specified URL using attacker-specified credentials. This issue arises because the plugin does not perform a permission check in an HTTP endpoint implementing form validation, allowing attackers with Overall/Read permission to exploit this vulnerability. The HTTP endpoint is also vulnerable because it does not require POST requests.

A missing permission check in the Jenkins mabl Plugin allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. The plugin does not perform permission checks in several HTTP endpoints, which also results in a cross-site request forgery (CSRF) vulnerability due to not requiring POST requests.

A missing permission check in the Jenkins Datadog Plugin allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs, capturing credentials stored in Jenkins. The issue is related to an HTTP endpoint that does not perform a permission check, enabling attackers to exploit this vulnerability.

A missing permission check in the Jenkins Orka by MacStadium Plugin allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified `credentials IDs` obtained through another method, capturing credentials stored in Jenkins. The issue is related to an HTTP endpoint that does not perform a permission check, enabling attackers to exploit this weakness.

A missing permission check in the plugin allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs, capturing credentials stored in Jenkins. The plugin does not perform permission checks in several HTTP endpoints, which also results in a cross-site request forgery (CSRF) vulnerability, as these endpoints do not require POST requests.

A cross-site request forgery (CSRF) vulnerability allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs, capturing credentials stored in Jenkins. The vulnerability is also characterized by a lack of permission checks in several HTTP endpoints, which can be exploited by attackers with Overall/Read permission. Additionally, these endpoints do not require POST requests, contributing to the CSRF vulnerability.

A missing permission check in the Jenkins Benchmark Evaluator Plugin allows attackers with Overall/Read permission to connect to an attacker-specified URL and to check for the existence of directories, `.csv`, and `.ycsb` files on the Jenkins controller file system. This issue also results in a cross-site request forgery (CSRF) vulnerability due to the form validation method not requiring POST requests.

The issue results in a stored cross-site scripting (XSS) vulnerability. This occurs because the plugin does not escape names of jobs used as building blocks for Template Workflow Job. Attackers who can create jobs may exploit this vulnerability.

The issue is related to a stored cross-site scripting vulnerability. It occurs because the file path and the project name for the Log file field form validation are not correctly escaped. This vulnerability can be exploited by attackers with Item/Configure permission.

A cross-site request forgery (CSRF) vulnerability allows attackers to connect to an attacker-specified URL. The issue arises from the lack of permission checks in several HTTP endpoints, which can be exploited by attackers with Overall/Read permission. These endpoints also do not require POST requests, contributing to the vulnerability.

A cross-site request forgery (CSRF) vulnerability allows attackers to connect to an attacker-specified URL and send an HTTP POST request with a JSON payload consisting of attacker-specified credentials.

The Nuxeo Platform is an open source content management platform for building business applications. In the affected version, the `oauth2` REST API is vulnerable to Reflected Cross-Site Scripting (XSS), which can be escalated to Remote Code Execution (RCE) by leveraging the automation API.