Vulnerabilities > Pulpproject > Pulp > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2018-08-15 | CVE-2018-10917 | Path Traversal vulnerability in Pulpproject Pulp pulp 2.16.x and possibly older is vulnerable to an improper path parsing. | 6.5 |
| 2018-06-18 | CVE-2018-1090 | Information Exposure vulnerability in multiple products In Pulp before version 2.16.2, secrets are passed into override_config when triggering a task and then become readable to all users with read access on the distributor/importer. | 5.0 |
| 2017-09-25 | CVE-2015-5263 | Improper Certificate Validation vulnerability in Pulpproject Pulp pulp-consumer-client 2.4.0 through 2.6.3 does not check the server's TLS certificate signatures when retrieving the server's public key upon registration. | 6.8 |
| 2017-06-13 | CVE-2016-3696 | Information Exposure vulnerability in multiple products The pulp-qpid-ssl-cfg script in Pulp before 2.8.5 allows local users to obtain the CA key. | 5.5 |
| 2017-06-08 | CVE-2016-3111 | Information Exposure vulnerability in Pulpproject Pulp pulp.spec in the installation process for Pulp 2.8.3 generates the RSA key pairs used to validate messages between the pulp server and pulp consumers in a directory that is world-readable before later modifying the permissions, which might allow local users to read the generated RSA keys via reading the key files while the installation process is running. | 5.5 |
| 2017-06-08 | CVE-2016-3107 | Improper Access Control vulnerability in Pulpproject Pulp The Node certificate in Pulp before 2.8.3 contains the private key, and is stored in a world-readable file in the "/etc/pki/pulp/nodes/" directory, which allows local users to gain access to sensitive data. | 5.5 |
| 2017-04-13 | CVE-2016-3106 | Race Condition vulnerability in Pulpproject Pulp 2.8.21 Pulp before 2.8.3 creates a temporary directory during CA key generation in an insecure manner. | 5.0 |
| 2017-04-03 | CVE-2013-7450 | Improper Certificate Validation vulnerability in Pulpproject Pulp 2.2.11 Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations. | 5.0 |