Viktor Gazdag

The issue is related to insufficient input validation in the User Interface component of the Oracle Communications Diameter Signaling Router (DSR) product. This allows a low-privileged attacker with network access via HTTP to compromise the system. Successful attacks require human interaction from a person other than the attacker and may significantly impact additional products. The exploitation can result in unauthorized update, insert, or delete access to some of the DSR's accessible data, as well as unauthorized read access to a subset of the DSR's accessible data.

The issue is related to insufficient input validation in the User Interface component of the Oracle Communications Diameter Signaling Router (DSR) product. This allows an unauthenticated attacker with network access via HTTP to compromise the system. Successful attacks require human interaction from a person other than the attacker and may significantly impact additional products. The exploitation can result in unauthorized update, insert, or delete access to some of the DSR's accessible data, as well as unauthorized read access to a subset of the DSR's accessible data.

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, potentially capturing credentials stored in Jenkins.

A cross-site request forgery issue allows attackers to connect to an attacker-specified web server using attacker-specified credentials.

The issue allows credentials to be stored unencrypted in the global configuration file on the Jenkins master. This can be viewed by users with access to the master file system.

A cross-site request forgery issue allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs, potentially capturing credentials stored in Jenkins.

The issue allows credentials to be stored unencrypted in job config.xml files on the Jenkins master. Users with Extended Read permission or access to the master file system can view these credentials.

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 form validation method does not require POST requests, resulting in a CSRF vulnerability.

A cross-site request forgery issue allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs, potentially capturing credentials stored in Jenkins. This is due to a lack of permission checks on a method implementing form validation, which can be exploited by users with Overall/Read access to Jenkins. The form validation method is also vulnerable as it does not require POST requests.

A missing permission check in form-related methods allows users with Overall/Read access to enumerate credentials ID of credentials stored in Jenkins.

A cross-site request forgery issue allows attackers to connect to an attacker-specified web server.

A missing permission check in the plugin allows attackers with Overall/Read permission to connect to an attacker-specified web server.

A cross-site request forgery issue allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs, potentially capturing the Kubernetes service account token or credentials stored in Jenkins.

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, potentially capturing the Kubernetes service account token or credentials stored in Jenkins.

The issue concerns a stored XSS vulnerability. It occurs because the plugin does not properly escape job display names and build names shown on its view. This can be exploited by attackers who have the ability to change these properties.

The issue results in a stored cross-site scripting vulnerability. It occurs because the plugin does not escape the description of builds shown in its view. This makes it exploitable by users who have the ability to change build descriptions.

A cross-site request forgery issue allows attackers to have Jenkins evaluate a computationally expensive regular expression, potentially leading to exploitation.

The issue allows credentials to be stored unencrypted in the global configuration file and in job config.xml files on the Jenkins master. This can be accessed by users with Extended Read permission or those who have access to the master file system.

The issue results in a stored XSS vulnerability, which can be exploited by attackers who can affect view content, such as job display names or pipeline stage names.

The issue concerns the storage of credentials in the global configuration file on the Jenkins master. Specifically, credentials are stored unencrypted, allowing users with access to the master file system to view them. This affects users with access to the Jenkins master.