Filtered by vendor Jenkins
Subscriptions
Total
1603 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2023-32986 | 1 Jenkins | 1 File Parameters | 2023-10-24 | 8.8 High |
Jenkins File Parameter Plugin 285.v757c5b_67a_c25 and earlier does not restrict the name (and resulting uploaded file name) of Stashed File Parameters, allowing attackers with Item/Configure permission to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content. | ||||
CVE-2023-32985 | 1 Jenkins | 1 Sidebar Link | 2023-10-24 | 4.3 Medium |
Jenkins Sidebar Link Plugin 2.2.1 and earlier does not restrict the path of files in a method implementing form validation, allowing attackers with Overall/Read permission to check for the existence of an attacker-specified file path on the Jenkins controller file system. | ||||
CVE-2023-32984 | 1 Jenkins | 1 Testng Results | 2023-10-24 | 5.4 Medium |
Jenkins TestNG Results Plugin 730.v4c5283037693 and earlier does not escape several values that are parsed from TestNG report files and displayed on the plugin's test information pages, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide a crafted TestNG report file. | ||||
CVE-2023-32983 | 1 Jenkins | 1 Ansible | 2023-10-24 | 5.3 Medium |
Jenkins Ansible Plugin 204.v8191fd551eb_f and earlier does not mask extra variables displayed on the configuration form, increasing the potential for attackers to observe and capture them. | ||||
CVE-2023-32982 | 1 Jenkins | 1 Ansible | 2023-10-24 | 4.3 Medium |
Jenkins Ansible Plugin 204.v8191fd551eb_f and earlier stores extra variables unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system. | ||||
CVE-2023-32981 | 1 Jenkins | 1 Pipeline Utility Steps | 2023-10-24 | 8.8 High |
An arbitrary file write vulnerability in Jenkins Pipeline Utility Steps Plugin 2.15.2 and earlier allows attackers able to provide crafted archives as parameters to create or replace arbitrary files on the agent file system with attacker-specified content. | ||||
CVE-2023-32980 | 1 Jenkins | 1 Email Extension | 2023-10-24 | 4.3 Medium |
A cross-site request forgery (CSRF) vulnerability in Jenkins Email Extension Plugin allows attackers to make another user stop watching an attacker-specified job. | ||||
CVE-2023-32979 | 1 Jenkins | 1 Email Extension | 2023-10-24 | 4.3 Medium |
Jenkins Email Extension Plugin does not perform a permission check in a method implementing form validation, allowing attackers with Overall/Read permission to check for the existence of files in the email-templates/ directory in the Jenkins home directory on the controller file system. | ||||
CVE-2023-32978 | 1 Jenkins | 1 Lightweight Directory Access Protocol | 2023-10-24 | 4.3 Medium |
A cross-site request forgery (CSRF) vulnerability in Jenkins LDAP Plugin allows attackers to connect to an attacker-specified LDAP server using attacker-specified credentials. | ||||
CVE-2023-32977 | 1 Jenkins | 1 Pipeline\ | 2023-10-24 | 5.4 Medium |
Jenkins Pipeline: Job Plugin does not escape the display name of the build that caused an earlier build to be aborted, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to set build display names immediately. | ||||
CVE-2023-30532 | 1 Jenkins | 1 Turboscript | 2023-10-24 | 6.5 Medium |
A missing permission check in Jenkins TurboScript Plugin 1.3 and earlier allows attackers with Item/Read permission to trigger builds of jobs corresponding to the attacker-specified repository. | ||||
CVE-2023-30531 | 1 Jenkins | 1 Consul Kv Builder | 2023-10-24 | 6.5 Medium |
Jenkins Consul KV Builder Plugin 2.0.13 and earlier does not mask the HashiCorp Consul ACL Token on the global configuration form, increasing the potential for attackers to observe and capture it. | ||||
CVE-2023-30530 | 1 Jenkins | 1 Consul Kv Builder | 2023-10-24 | 4.3 Medium |
Jenkins Consul KV Builder Plugin 2.0.13 and earlier stores the HashiCorp Consul ACL Token unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system. | ||||
CVE-2023-30529 | 1 Jenkins | 1 Lucene-search | 2023-10-24 | 4.3 Medium |
Jenkins Lucene-Search Plugin 387.v938a_ecb_f7fe9 and earlier does not require POST requests for an HTTP endpoint, allowing attackers to reindex the database. | ||||
CVE-2023-30528 | 1 Jenkins | 1 Wso2 Oauth | 2023-10-24 | 6.5 Medium |
Jenkins WSO2 Oauth Plugin 1.0 and earlier does not mask the WSO2 Oauth client secret on the global configuration form, increasing the potential for attackers to observe and capture it. | ||||
CVE-2023-30527 | 1 Jenkins | 1 Wso2 Oauth | 2023-10-24 | 4.3 Medium |
Jenkins WSO2 Oauth Plugin 1.0 and earlier stores the WSO2 Oauth client secret unencrypted in the global config.xml file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system. | ||||
CVE-2023-30526 | 1 Jenkins | 1 Report Portal | 2023-10-24 | 6.5 Medium |
A missing permission check in Jenkins Report Portal Plugin 0.5 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified bearer token authentication. | ||||
CVE-2023-30525 | 1 Jenkins | 1 Report Portal | 2023-10-24 | 8.8 High |
A cross-site request forgery (CSRF) vulnerability in Jenkins Report Portal Plugin 0.5 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified bearer token authentication. | ||||
CVE-2023-30524 | 1 Jenkins | 1 Report Portal | 2023-10-24 | 4.3 Medium |
Jenkins Report Portal Plugin 0.5 and earlier does not mask ReportPortal access tokens displayed on the configuration form, increasing the potential for attackers to observe and capture them. | ||||
CVE-2023-30523 | 1 Jenkins | 1 Report Portal | 2023-10-24 | 4.3 Medium |
Jenkins Report Portal Plugin 0.5 and earlier stores ReportPortal access tokens unencrypted in job config.xml files on the Jenkins controller as part of its configuration where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system. |