本頁列出影響 pulpproject pulp 的已公開 CVE 漏洞（透過 NVD CPE 關聯）。每列包含嚴重程度評分、摘要與發布日期，便於識別與分析安全議題。
| CVE | 摘要 | 來源 | 最高 CVSS | EPSS % | 公開時間 | 更新時間 |
|---|---|---|---|---|---|---|
| CVE-2024-7143 | 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 permissi | [email protected] | 8.3 | 0.61% | 2024-08-07 | 2026-03-20 |
| CVE-2018-10917 | 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. | [email protected] | 6.8 | 1.07% | 2018-08-15 | 2024-11-21 |
| 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 access can then view these secrets. | [email protected] | 5.5 | 1.34% | 2018-06-18 | 2024-11-21 |
| 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. | [email protected] | 8.1 | 0.87% | 2017-09-25 | 2026-05-13 |
| CVE-2016-3704 | Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords. | [email protected] | 7.5 | 1.94% | 2017-06-13 | 2026-05-13 |
| CVE-2016-3696 | The pulp-qpid-ssl-cfg script in Pulp before 2.8.5 allows local users to obtain the CA key. | [email protected] | 5.5 | 0.36% | 2017-06-13 | 2026-05-13 |
| CVE-2016-3095 | server/bin/pulp-gen-ca-certificate in Pulp before 2.8.2 allows local users to read the generated private key. | [email protected] | 5.5 | 0.30% | 2017-06-08 | 2026-05-13 |
| 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 private keys and escalate privileges by reading /etc/pki/pulp/consumer/consumer-cert, and authenticating as a consumer user. | [email protected] | 7.5 | 2.19% | 2017-06-08 | 2026-05-13 |
| 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 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. | [email protected] | 5.5 | 0.39% | 2017-06-08 | 2026-05-13 |
| 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. | [email protected] | 7.1 | 0.26% | 2017-06-08 | 2026-05-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 data. | [email protected] | 5.5 | 0.20% | 2017-06-08 | 2026-05-13 |
| CVE-2016-3106 | Pulp before 2.8.3 creates a temporary directory during CA key generation in an insecure manner. | [email protected] | 5.3 | 0.94% | 2017-04-13 | 2026-05-13 |
| CVE-2013-7450 | Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations. | [email protected] | 7.5 | 0.87% | 2017-04-03 | 2026-05-13 |