Pulp Pulpproject Pulp

Do you want an email whenever new security vulnerabilities are reported in Pulpproject Pulp?

By the Year

In 2024 there have been 0 vulnerabilities in Pulpproject Pulp . Pulp did not have any published security vulnerabilities last year.

Year Vulnerabilities Average Score
2024 0 0.00
2023 0 0.00
2022 0 0.00
2021 0 0.00
2020 0 0.00
2019 0 0.00
2018 2 7.00

It may take a day or so for new Pulp vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Pulpproject Pulp Security Vulnerabilities

pulp 2.16.x and possibly older is vulnerable to an improper path parsing

CVE-2018-10917 6.5 - Medium - August 15, 2018

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.

Directory traversal

In Pulp before version 2.16.2

CVE-2018-1090 7.5 - High - June 18, 2018

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.

Information Disclosure

Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords.

CVE-2016-3704 7.5 - High - June 13, 2017

Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords.

Credentials Management Errors

The pulp-qpid-ssl-cfg script in Pulp before 2.8.5

CVE-2016-3696 5.5 - Medium - June 13, 2017

The pulp-qpid-ssl-cfg script in Pulp before 2.8.5 allows local users to obtain the CA key.

Information Disclosure

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

CVE-2016-3112 7.5 - High - June 08, 2017

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.

Authorization

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

CVE-2016-3111 5.5 - Medium - June 08, 2017

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.

Information Disclosure

The pulp-gen-nodes-certificate script in Pulp before 2.8.3

CVE-2016-3108 7.1 - High - June 08, 2017

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.

insecure temporary file

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

CVE-2016-3107 5.5 - Medium - June 08, 2017

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.

Authorization

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Pulpproject Pulp or by Pulpproject? Click the Watch button to subscribe.

Pulpproject
Vendor

subscribe