Sweet B vulnerabilitiesRanked by how likely they are to be used.
Sweet B is made by Westerndigital. We track 4 published vulnerabilities in it, across 2 versions. None of them is on the list of flaws known to be exploited today. If you run Sweet B, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Sweet B vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Sweet B's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Sweet B 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.7%CVE-2022-23001Medium
When compressing or decompressing elliptic curve points using the Sweet B library, an incorrect choice of sign bit is used.
- 0.7%CVE-2022-23002Medium
When compressing or decompressing a point on the NIST P-256 elliptic curve with an X coordinate of zero, the resulting output is not properly reduced modulo the P-256 field prime and is invalid.
- 0.7%CVE-2022-23003Medium
When computing a shared secret or point multiplication on the NIST P-256 curve that results in an X coordinate of zero, the resulting output is not properly reduced modulo the P-256 field prime and is invalid.
- 0.7%CVE-2022-23004Medium
When computing a shared secret or point multiplication on the NIST P-256 curve using a public key with an X coordinate of zero, an error is returned from the library, and an invalid unreduced value is written to the...
Running Sweet B? 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 compressing or decompressing elliptic curve points using the Sweet B library, an incorrect choice of sign bit is used. An attacker with user level privileges and no other user's assistance can exploit this vulnerability with only knowledge of the public key and the library. The resulting output may cause an error when used in other operations; for instance, verification of a valid signature under a decompressed public key may fail. This may be leveraged by an attacker to cause an error scenario in applications which use the library, resulting in a limited denial of service for an individual user. The scope of impact cannot extend to other components.
- Matched to
- Sweet B 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 Sweet B, across 2 versions.
None of Sweet B's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Sweet B. 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.