pulpproject vulnerabilities

Products

• pulp 13
• pulp ansible 1
• qpid 1

Latest pulpproject CVEs

Newest publication first

1. CVE-2024-7143 Pulpcore: rbac permissions incorrectly assigned in tasks that create objects

   Published 2024-08-07

   High·CVSS 8.3 EPSS 0.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 cu...

2. CVE-2022-3644 Plaintext storage of tokens in pulp_ansible

   Published 2022-10-25

   Medium·CVSS 5.5 EPSS 0.30%

   The collection remote for pulp_ansible stores tokens in plaintext instead of using pulp's encrypted field and exposes them in read/write mode via the API () instead of marking it as write only.

3. CVE-2018-10917 Withdrawn Advisory: Pulp Improper Path Parsing

   Published 2018-08-15

   Medium·CVSS 6.5 EPSS 1.1%

   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.

4. CVE-2018-1090 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 a...

   Published 2018-06-18

   High·CVSS 7.5 EPSS 1.3%

   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.

5. CVE-2015-5164 The Qpid server on Red Hat Satellite 6 does not properly restrict message types, which allows remote authenticated users with administrative access on a managed content host to execute arbitrary code....

   Published 2017-10-18

   High·CVSS 7.2 EPSS 4.0%

   The Qpid server on Red Hat Satellite 6 does not properly restrict message types, which allows remote authenticated users with administrative access on a managed content host to execute arbitrary code via a crafted message, related to a pickle processing problem in pulp.

6. CVE-2015-5263 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.

   Published 2017-09-25

   High·CVSS 8.1 EPSS 0.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.

7. CVE-2016-3704 Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords.

   Published 2017-06-13

   High·CVSS 7.5 EPSS 2.0%

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

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

   Published 2017-06-13

   Medium·CVSS 5.5 EPSS 0.35%

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

9. CVE-2016-3095 server/bin/pulp-gen-ca-certificate in Pulp before 2.8.2 allows local users to read the generated private key.

   Published 2017-06-08

   Medium·CVSS 5.5 EPSS 0.30%

   server/bin/pulp-gen-ca-certificate in Pulp before 2.8.2 allows local users to read the generated private key.

10. CVE-2016-3112 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 pr...

    Published 2017-06-08

    High·CVSS 7.5 EPSS 2.2%

    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-ce...

11. CVE-2016-3111 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...

    Published 2017-06-08

    Medium·CVSS 5.5 EPSS 0.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...

12. CVE-2016-3108 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.

    Published 2017-06-08

    High·CVSS 7.1 EPSS 0.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.

13. CVE-2016-3107 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...

    Published 2017-06-08

    Medium·CVSS 5.5 EPSS 0.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.

14. CVE-2016-3106 Pulp before 2.8.3 creates a temporary directory during CA key generation in an insecure manner.

    Published 2017-04-13

    Medium·CVSS 5.3 EPSS 0.94%

    Pulp before 2.8.3 creates a temporary directory during CA key generation in an insecure manner.

15. CVE-2013-7450 Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations.

    Published 2017-04-03

    High·CVSS 7.5 EPSS 0.87%

    Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.