Export limit exceeded: 74343 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (74343 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2019-10476 | 1 Jenkins | 1 Zulip | 2024-11-21 | 7.8 High |
| Jenkins Zulip Plugin 1.1.0 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they could be viewed by users with access to the master file system. | ||||
| CVE-2019-10471 | 1 Jenkins | 1 Libvirt Slaves | 2024-11-21 | 8.8 High |
| A cross-site request forgery vulnerability in Jenkins Libvirt Slaves Plugin allows attackers to connect to an attacker-specified SSH server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. | ||||
| CVE-2019-10468 | 1 Jenkins | 1 Kubernetes Ci | 2024-11-21 | 8.8 High |
| A cross-site request forgery vulnerability in Jenkins ElasticBox Jenkins Kubernetes CI/CD Plugin allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. | ||||
| CVE-2019-10466 | 1 Jenkins | 1 360 Fireline | 2024-11-21 | 8.1 High |
| An XML external entities (XXE) vulnerability in Jenkins 360 FireLine Plugin allows attackers with Overall/Read access to have Jenkins resolve external entities, resulting in the extraction of secrets from the Jenkins agent, server-side request forgery, or denial-of-service attacks. | ||||
| CVE-2019-10464 | 1 Jenkins | 1 Deploy Weblogic | 2024-11-21 | 8.8 High |
| A cross-site request forgery vulnerability in Jenkins Deploy WebLogic Plugin allows attackers to connect to an attacker-specified URL using attacker-specified credentials, or determine whether a file or directory with an attacker-specified path exists on the Jenkins master file system. | ||||
| CVE-2019-10462 | 1 Jenkins | 1 Dynatrace Application Monitoring | 2024-11-21 | 8.1 High |
| A cross-site request forgery vulnerability in Jenkins Dynatrace Application Monitoring Plugin 2.1.3 and earlier allowed attackers to connect to an attacker-specified URL using attacker-specified credentials. | ||||
| CVE-2019-10461 | 1 Jenkins | 1 Dynatrace Application Monitoring | 2024-11-21 | 7.8 High |
| Jenkins Dynatrace Application Monitoring Plugin 2.1.3 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they could be viewed by users with access to the master file system. | ||||
| CVE-2019-10460 | 1 Jenkins | 1 Bitbucket Oauth | 2024-11-21 | 7.8 High |
| Jenkins Bitbucket OAuth Plugin 0.9 and earlier stored credentials unencrypted in the global config.xml configuration file on the Jenkins master where they could be viewed by users with access to the master file system. | ||||
| CVE-2019-10453 | 1 Jenkins | 1 Delphix | 2024-11-21 | 7.8 High |
| Jenkins Delphix Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master file system. | ||||
| CVE-2019-10449 | 1 Jenkins | 1 Fortify On Demand | 2024-11-21 | 8.8 High |
| Jenkins Fortify on Demand Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system. | ||||
| CVE-2019-10448 | 1 Jenkins | 1 Extensive Testing | 2024-11-21 | 8.8 High |
| Jenkins Extensive Testing Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system. | ||||
| CVE-2019-10446 | 1 Jenkins | 1 Cadence Vmanager | 2024-11-21 | 8.2 High |
| Jenkins Cadence vManager Plugin 2.7.0 and earlier disabled SSL/TLS and hostname verification globally for the Jenkins master JVM. | ||||
| CVE-2019-10443 | 1 Jenkins | 1 Icescrum | 2024-11-21 | 8.8 High |
| Jenkins iceScrum Plugin 1.1.4 and earlier stored credentials unencrypted in job config.xml files on the Jenkins master where they could be viewed by users with Extended Read permission, or access to the master file system. | ||||
| CVE-2019-10440 | 1 Jenkins | 1 Neoload | 2024-11-21 | 8.8 High |
| Jenkins NeoLoad Plugin 2.2.5 and earlier stored credentials unencrypted in its global configuration file and in job config.xml files on the Jenkins master where they could be viewed by users with Extended Read permission, or access to the master file system. | ||||
| CVE-2019-10437 | 1 Jenkins | 1 Crx Content Package Deployer | 2024-11-21 | 8.8 High |
| A cross-site request forgery vulnerability in Jenkins CRX Content Package Deployer Plugin 1.8.1 and earlier allowed attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. | ||||
| CVE-2019-10435 | 1 Jenkins | 1 Sourcegear Vault | 2024-11-21 | 7.5 High |
| Jenkins SourceGear Vault Plugin transmits configured credentials in plain text as part of job configuration forms, potentially resulting in their exposure. | ||||
| CVE-2019-10434 | 1 Jenkins | 1 Ldap Email | 2024-11-21 | 7.5 High |
| Jenkins LDAP Email Plugin transmits configured credentials in plain text as part of the global Jenkins configuration form, potentially resulting in their exposure. | ||||
| CVE-2019-10428 | 1 Jenkins | 1 Aqua Security Scanner | 2024-11-21 | 7.5 High |
| Jenkins Aqua Security Scanner Plugin 3.0.17 and earlier transmitted configured credentials in plain text as part of the global Jenkins configuration form, potentially resulting in their exposure. | ||||
| CVE-2019-10412 | 1 Jenkins | 1 Inedo Proget | 2024-11-21 | 7.5 High |
| Jenkins Inedo ProGet Plugin 1.2 and earlier transmitted configured credentials in plain text as part of the global Jenkins configuration form, potentially resulting in their exposure. | ||||
| CVE-2019-10411 | 1 Jenkins | 1 Inedo Buildmaster | 2024-11-21 | 7.5 High |
| Jenkins Inedo BuildMaster Plugin 2.4.0 and earlier transmitted configured credentials in plain text as part of the global Jenkins configuration form, potentially resulting in their exposure. | ||||