Filtered by vendor Jenkins
Subscribe
Total
1608 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2017-1000503 | 1 Jenkins | 1 Jenkins | 2024-02-28 | 6.8 MEDIUM | 8.1 HIGH |
A race condition during Jenkins 2.81 through 2.94 (inclusive); 2.89.1 startup could result in the wrong order of execution of commands during initialization. This could in rare cases result in failure to initialize the setup wizard on the first startup. This resulted in multiple security-related settings not being set to their usual strict default. | |||||
CVE-2017-2611 | 2 Jenkins, Redhat | 2 Jenkins, Openshift | 2024-02-28 | 4.0 MEDIUM | 4.3 MEDIUM |
Jenkins before versions 2.44, 2.32.2 is vulnerable to an insufficient permission check for periodic processes (SECURITY-389). The URLs /workspaceCleanup and /fingerprintCleanup did not perform permission checks, allowing users with read access to Jenkins to trigger these background processes (that are otherwise performed daily), possibly causing additional load on Jenkins master and agents. | |||||
CVE-2017-1000243 | 1 Jenkins | 1 Favorite Plugin | 2024-02-28 | 4.0 MEDIUM | 4.3 MEDIUM |
Jenkins Favorite Plugin 2.1.4 and older does not perform permission checks when changing favorite status, allowing any user to set any other user's favorites | |||||
CVE-2017-1000091 | 1 Jenkins | 1 Github Branch Source | 2024-02-28 | 6.8 MEDIUM | 6.3 MEDIUM |
GitHub Branch Source Plugin connects to a user-specified GitHub API URL (e.g. GitHub Enterprise) as part of form validation and completion (e.g. to verify Scan Credentials are correct). This functionality improperly checked permissions, allowing any user with Overall/Read access to Jenkins to connect to any web server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery. | |||||
CVE-2017-1000086 | 1 Jenkins | 1 Periodic Backup | 2024-02-28 | 6.0 MEDIUM | 8.0 HIGH |
The Periodic Backup Plugin did not perform any permission checks, allowing any user with Overall/Read access to change its settings, trigger backups, restore backups, download backups, and also delete all previous backups via log rotation. Additionally, the plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. | |||||
CVE-2017-1000093 | 1 Jenkins | 1 Poll Scm | 2024-02-28 | 6.8 MEDIUM | 8.8 HIGH |
Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to initiate polling of projects with a known name. While Jenkins in general does not consider polling to be a protection-worthy action as it's similar to cache invalidation, the plugin specifically adds a permission to be able to use this functionality, and this issue undermines that permission. | |||||
CVE-2014-9635 | 2 Apache, Jenkins | 2 Tomcat, Jenkins | 2024-02-28 | 5.0 MEDIUM | 5.3 MEDIUM |
Jenkins before 1.586 does not set the HttpOnly flag in a Set-Cookie header for session cookies when run on Tomcat 7.0.41 or later, which makes it easier for remote attackers to obtain potentially sensitive information via script access to cookies. | |||||
CVE-2017-1000362 | 1 Jenkins | 1 Jenkins | 2024-02-28 | 5.0 MEDIUM | 9.8 CRITICAL |
The re-key admin monitor was introduced in Jenkins 1.498 and re-encrypted all secrets in JENKINS_HOME with a new key. It also created a backup directory with all old secrets, and the key used to encrypt them. These backups were world-readable and not removed afterwards. Jenkins now deletes the backup directory, if present. Upgrading from before 1.498 will no longer create a backup directory. Administrators relying on file access permissions in their manually created backups are advised to check them for the directory $JENKINS_HOME/jenkins.security.RekeySecretAdminMonitor/backups, and delete it if present. | |||||
CVE-2017-1000090 | 1 Jenkins | 1 Role-based Authorization Strategy | 2024-02-28 | 6.8 MEDIUM | 8.8 HIGH |
Role-based Authorization Strategy Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to add administrator role to any user, or to remove the authorization configuration, preventing legitimate access to Jenkins. | |||||
CVE-2017-1000108 | 1 Jenkins | 1 Pipeline-input-step | 2024-02-28 | 5.0 MEDIUM | 7.5 HIGH |
The Pipeline: Input Step Plugin by default allowed users with Item/Read access to a pipeline to interact with the step to provide input. This has been changed, and now requires users to have the Item/Build permission instead. | |||||
CVE-2017-1000245 | 1 Jenkins | 1 Ssh | 2024-02-28 | 5.0 MEDIUM | 9.8 CRITICAL |
The SSH Plugin stores credentials which allow jobs to access remote servers via the SSH protocol. User passwords and passphrases for encrypted SSH keys are stored in plaintext in a configuration file. | |||||
CVE-2017-1000087 | 1 Jenkins | 1 Github Branch Source | 2024-02-28 | 4.0 MEDIUM | 4.3 MEDIUM |
GitHub Branch Source provides a list of applicable credential IDs to allow users configuring a job to select the one they'd like to use. This functionality did not check permissions, allowing any user with Overall/Read permission to get a list of valid credentials IDs. Those could be used as part of an attack to capture the credentials using another vulnerability. | |||||
CVE-2017-1000089 | 1 Jenkins | 1 Pipeline\ | 2024-02-28 | 5.0 MEDIUM | 5.3 MEDIUM |
Builds in Jenkins are associated with an authentication that controls the permissions that the build has to interact with other elements in Jenkins. The Pipeline: Build Step Plugin did not check the build authentication it was running as and allowed triggering any other project in Jenkins. | |||||
CVE-2017-1000109 | 1 Jenkins | 1 Owasp Dependency-check | 2024-02-28 | 4.3 MEDIUM | 6.1 MEDIUM |
The custom Details view of the Static Analysis Utilities based OWASP Dependency-Check Plugin, was vulnerable to a persisted cross-site scripting vulnerability: Malicious users able to influence the input to this plugin could insert arbitrary HTML into this view. | |||||
CVE-2017-1000114 | 1 Jenkins | 1 Datadog | 2024-02-28 | 4.3 MEDIUM | 3.1 LOW |
The Datadog Plugin stores an API key to access the Datadog service in the global Jenkins configuration. While the API key is stored encrypted on disk, it was transmitted in plain text as part of the configuration form. This could result in exposure of the API key for example through browser extensions or cross-site scripting vulnerabilities. The Datadog Plugin now encrypts the API key transmitted to administrators viewing the global configuration form. | |||||
CVE-2017-1000244 | 1 Jenkins | 1 Favorite | 2024-02-28 | 6.8 MEDIUM | 8.8 HIGH |
Jenkins Favorite Plugin version 2.2.0 and older is vulnerable to CSRF resulting in data modification | |||||
CVE-2017-1000095 | 1 Jenkins | 1 Script Security | 2024-02-28 | 4.0 MEDIUM | 6.5 MEDIUM |
The default whitelist included the following unsafe entries: DefaultGroovyMethods.putAt(Object, String, Object); DefaultGroovyMethods.getAt(Object, String). These allowed circumventing many of the access restrictions implemented in the script sandbox by using e.g. currentBuild['rawBuild'] rather than currentBuild.rawBuild. Additionally, the following entries allowed accessing private data that would not be accessible otherwise due to script security: groovy.json.JsonOutput.toJson(Closure); groovy.json.JsonOutput.toJson(Object). | |||||
CVE-2017-1000102 | 1 Jenkins | 1 Static Analysis Utilities | 2024-02-28 | 3.5 LOW | 5.4 MEDIUM |
The Details view of some Static Analysis Utilities based plugins, was vulnerable to a persisted cross-site scripting vulnerability: Malicious users able to influence the input to these plugins, for example the console output which is parsed to extract build warnings (Warnings Plugin), could insert arbitrary HTML into this view. | |||||
CVE-2017-1000094 | 1 Jenkins | 1 Docker Commons | 2024-02-28 | 4.0 MEDIUM | 6.5 MEDIUM |
Docker Commons Plugin provides a list of applicable credential IDs to allow users configuring a job to select the one they'd like to use to authenticate with a Docker Registry. This functionality did not check permissions, allowing any user with Overall/Read permission to get a list of valid credentials IDs. Those could be used as part of an attack to capture the credentials using another vulnerability. | |||||
CVE-2017-1000113 | 1 Jenkins | 1 Deploy | 2024-02-28 | 2.1 LOW | 5.5 MEDIUM |
The Deploy to container Plugin stored passwords unencrypted as part of its configuration. This allowed users with Jenkins master local file system access, or users with Extended Read access to the jobs it is used in, to retrieve those passwords. The Deploy to container Plugin now integrates with Credentials Plugin to store passwords securely, and automatically migrates existing passwords. |