CVE-2022-23001: Sweet-B Library: Point compress/decompress using the wrong bit for sign

Published Jul 29, 2022
·
Updated

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.

Affected Software

1 affected component
WesternDigital Sweet B=1

Remediation

Information

The vulnerability was addressed by correcting the choice of sign bit in the affected routines. To get the latest version of the Sweet B library, update your local repository from https://github.com/westerndigitalcorporation/sweet-b

Event History

Jul 29, 2022
CVE Published
via MITRE·06:51 PM
Data Sourced
via MITRE·06:51 PM
RemedyDescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2022-23001?

CVE-2022-23001 is a vulnerability that occurs when compressing or decompressing elliptic curve points using the Sweet B library, where an incorrect choice of sign bit is used.

2

What is the severity of CVE-2022-23001?

The severity of CVE-2022-23001 is medium, with a severity value of 5.3.

3

How can an attacker exploit CVE-2022-23001?

An attacker with user level privileges and knowledge of the public key and the library can exploit CVE-2022-23001.

4

What software is affected by CVE-2022-23001?

The Sweet B library version 1 by Western Digital is affected by CVE-2022-23001.

5

How can I fix CVE-2022-23001?

To fix CVE-2022-23001, it is recommended to update to a patched version of the Sweet B library provided by Western Digital.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203