Pulpproject vulnerabilitiesNone on the known-exploited list.
Pulpproject has 15 published vulnerabilities across 3 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Pulp, with 13. If you run Pulpproject software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Pulpproject products have the most vulnerabilities?
Pulp leads with 13 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Pulpproject vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Pulpproject's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Pulpproject flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 4.0%CVE-2015-5164High
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...
- 2.2%CVE-2016-3112High
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...
- 2.0%CVE-2016-3704High
Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords.
- 1.3%CVE-2018-1090High
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.
- 1.1%CVE-2018-10917Medium
pulp 2.16.x and possibly older is vulnerable to an improper path parsing.
- 0.9%CVE-2016-3106Medium
Pulp before 2.8.3 creates a temporary directory during CA key generation in an insecure manner.
- 0.9%CVE-2013-7450High
Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations.
- 0.9%CVE-2015-5263High
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.
- 0.6%CVE-2024-7143High
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...
- 0.4%CVE-2016-3111Medium
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...
All Pulpproject products we track.
2 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
This directory lists the 2 Pulpproject products with at least one tracked version, of 3 in our catalogue.
Running Pulpproject? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Pulp on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 15 published vulnerabilities across 3 products and 108 versions from Pulpproject.
None of Pulpproject's vulnerabilities is on the list of flaws known to be exploited today.
Pulp, with 13 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Pulpproject products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.