Connect2id vulnerabilitiesNone on the known-exploited list.
Connect2id has 5 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Nimbus Jose+jwt, with 5. If you run Connect2id software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Connect2id products have the most vulnerabilities?
Nimbus Jose+jwt leads with 5 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Connect2id vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Connect2id's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Connect2id 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.
- 11%CVE-2019-17195Critical
Connect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught exceptions while parsing a JWT, which could result in an application crash (potential information disclosure) or a potential authentication bypass.
- 1.3%CVE-2017-12974High
Nimbus JOSE+JWT before 4.36 proceeds with ECKey construction without ensuring that the public x and y coordinates are on the specified curve, which allows attackers to conduct an Invalid Curve Attack in environments...
- 0.9%CVE-2017-12972High
In Nimbus JOSE+JWT before 4.39, there is no integer-overflow check when converting length values from bytes to bits, which allows attackers to conduct HMAC bypass attacks by shifting Additional Authenticated Data...
- 0.8%CVE-2023-52428High
In Connect2id Nimbus JOSE+JWT before 9.37.2, an attacker can cause a denial of service (resource consumption) via a large JWE p2c header value (aka iteration count) for the PasswordBasedDecrypter (PBKDF2) component.
- 0.6%
Nimbus JOSE+JWT before 4.39 proceeds improperly after detection of an invalid HMAC in authenticated AES-CBC decryption, which allows attackers to conduct a padding oracle attack.
All Connect2id products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Connect2id? 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
Connect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught exceptions while parsing a JWT, which could result in an application crash (potential information disclosure) or a potential authentication bypass.
- Matched to
- Connect2id 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 5 published vulnerabilities across 1 product and 279 versions from Connect2id.
None of Connect2id's vulnerabilities is on the list of flaws known to be exploited today.
Nimbus Jose+jwt, with 5 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Connect2id 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.