Pulpproject Pulp vulnerabilities
13 vulnerabilities
Known vulnerabilities in Pulpproject Pulp, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2018-1090fedoraprojectfedora+3
EPSS score1.34%
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. An attacker with API access can then view these secrets.CVE-2018-10917pulpprojectpulp+48EPSS score1.07%
pulp 2.16.x and possibly older is vulnerable to an improper path parsing. A malicious user or a malicious iso feed repository can write to locations accessible to the 'apache' user. This may lead to overwrite of published content on other iso repositories.CVE-2013-7450pulpprojectpulpEPSS score0.87%
Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations.CVE-2015-5263pulpprojectpulpEPSS score0.87%
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.CVE-2016-3704fedoraprojectfedora+1EPSS score1.98%
Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords.CVE-2016-3108pulpprojectpulpEPSS score0.26%
The pulp-gen-nodes-certificate script in Pulp before 2.8.3 allows local users to leak the keys or write to arbitrary files via a symlink attack.CVE-2016-3112pulpprojectpulpEPSS score2.19%
client/consumer/cli.py in Pulp before 2.8.3 writes consumer private keys to etc/pki/pulp/consumer/consumer-cert.pem as world-readable, which allows remote authenticated users to obtain the consumer private keys and escalate privileges by reading /etc/pki/pulp/consumer/consumer-cert, and authenticating as a consumer user.CVE-2016-3095fedoraprojectfedora+1EPSS score0.30%
server/bin/pulp-gen-ca-certificate in Pulp before 2.8.2 allows local users to read the generated private key.CVE-2016-3107pulpprojectpulpEPSS score0.20%
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.CVE-2016-3111pulpprojectpulpEPSS score0.39%
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.CVE-2016-3696fedoraprojectfedora+1EPSS score0.35%
The pulp-qpid-ssl-cfg script in Pulp before 2.8.5 allows local users to obtain the CA key.CVE-2016-3106pulpprojectpulpEPSS score0.94%
Pulp before 2.8.3 creates a temporary directory during CA key generation in an insecure manner.CVE-2024-7143chainguardpy3-pulp+6EPSS score0.61%
A flaw was found in the Pulp package. When a role-based access control (RBAC) object in Pulp is set to assign permissions on its creation, it uses the `AutoAddObjPermsMixin` (typically the add_roles_for_object_creator method). This method finds the object creator by checking the current authenticated user. For objects that are created within a task, this current user is set by the first user with any permissions on the task object. This means the oldest user with model/domain-level task permissions will always be set as the current user of a task, even if they didn't dispatch the task. Therefore, all objects created in tasks will have their permissions assigned to this oldest user, and the creating user will receive nothing.