Continuous Delivery vulnerabilitiesRanked by how likely they are to be used.
Continuous Delivery is made by Puppet. We track 4 published vulnerabilities in it, across 49 versions. None of them is on the list of flaws known to be exploited today. If you run Continuous Delivery, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Continuous Delivery vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Continuous Delivery's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Continuous Delivery 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.
- 0.9%CVE-2019-10695Medium
When using the cd4pe::root_configuration task to configure a Continuous Delivery for PE installation, the root user’s username and password were exposed in the job’s Job Details pane in the PE console.
- 0.9%CVE-2020-7944High
In Continuous Delivery for Puppet Enterprise (CD4PE) before 3.4.0, changes to resources or classes containing Sensitive parameters can result in the Sensitive parameters ending up in the impact analysis report.
- 0.8%CVE-2021-27024High
A flaw was discovered in Continuous Delivery for Puppet Enterprise (CD4PE) that results in a user with lower privileges being able to access a Puppet Enterprise API token.
- 0.3%CVE-2020-7945Medium
Local registry credentials were included directly in the CD4PE deployment definition, which could expose these credentials to users who should not have access to them.
Running Continuous Delivery? 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
When using the cd4pe::root_configuration task to configure a Continuous Delivery for PE installation, the root user’s username and password were exposed in the job’s Job Details pane in the PE console. These issues have been resolved in version 1.2.1 of the puppetlabs/cd4pe module.
- Matched to
- Continuous Delivery 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.
We track 4 published vulnerabilities listed under the name Continuous Delivery, across 49 versions.
None of Continuous Delivery's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Continuous Delivery. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.