Github Pull Request Coverage Status vulnerabilitiesRanked by how likely they are to be used.
Github Pull Request Coverage Status is made by Jenkins. We track 1 published vulnerability in it, across 34 versions. None of them is on the list of flaws known to be exploited today. If you run Github Pull Request Coverage Status, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Github Pull Request Coverage Status vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Github Pull Request Coverage Status's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Github Pull Request Coverage Status 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.2%CVE-2023-24442Medium
Jenkins GitHub Pull Request Coverage Status Plugin 2.2.0 and earlier stores the GitHub Personal Access Token, Sonar access token and Sonar password unencrypted in its global configuration file on the Jenkins...
Running Github Pull Request Coverage Status? 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
Jenkins GitHub Pull Request Coverage Status Plugin 2.2.0 and earlier stores the GitHub Personal Access Token, Sonar access token and Sonar password unencrypted in its global configuration file on the Jenkins controller where they can be viewed by users with access to the Jenkins controller file system.
- Matched to
- Github Pull Request Coverage Status 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 1 published vulnerability listed under the name Github Pull Request Coverage Status, across 34 versions.
None of Github Pull Request Coverage Status's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Github Pull Request Coverage Status. 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.