Github Oauth vulnerabilitiesRanked by how likely they are to be used.
Github Oauth is made by Jenkins. We track 2 published vulnerabilities in it, across 37 versions. None of them is on the list of flaws known to be exploited today. If you run Github Oauth, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Github Oauth vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Github Oauth's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Github Oauth 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.
- 1.1%CVE-2019-1003018Medium
An exposure of sensitive information vulnerability exists in Jenkins GitHub Authentication Plugin 0.29 and earlier in GithubSecurityRealm/config.jelly that allows attackers able to view a Jenkins administrator's web...
- 0.9%CVE-2019-1003019Medium
An session fixation vulnerability exists in Jenkins GitHub Authentication Plugin 0.29 and earlier in GithubSecurityRealm.java that allows unauthorized attackers to impersonate another user if they can control the...
Running Github Oauth? 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
An exposure of sensitive information vulnerability exists in Jenkins GitHub Authentication Plugin 0.29 and earlier in GithubSecurityRealm/config.jelly that allows attackers able to view a Jenkins administrator's web browser output, or control the browser (e.g. malicious extension) to retrieve the configured client secret.
- Matched to
- Github Oauth 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 2 published vulnerabilities listed under the name Github Oauth, across 37 versions.
None of Github Oauth's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Github Oauth. 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.