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

> An attacker can cause denial of service in applications using the Sweet B library by exploiting incorrect sign bit handling during elliptic curve point compression.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2022
- **Updated:** 3 Aug 2024

## What is CVE-2022-23001?

CVE-2022-23001 is a medium-severity vulnerability in Western Digital Sweet B Library, published on 29 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-682 (Incorrect Calculation)

## Which versions are affected by CVE-2022-23001?

It affects 1 product.


Products: Westerndigital Sweet B.

## How do I fix CVE-2022-23001?

No fix has been published for CVE-2022-23001 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-23001 being exploited?

There is no known exploitation of CVE-2022-23001 in the wild and no public exploit code.

## Other vulnerabilities in Western Digital Sweet B Library

- [CVE-2022-23002](https://insights.sbomify.com/CVE-2022-23002/): Point Compression/Decompression of NIST P-256 points with X coordinate of zero (medium 5.3)
- [CVE-2022-23003](https://insights.sbomify.com/CVE-2022-23003/): Shared secret or Point multiplication of NIST P-256 points with X coordinate of zero (medium 5.3)
- [CVE-2022-23004](https://insights.sbomify.com/CVE-2022-23004/): Algorithm incorrectly returning error and Invalid unreduced value written to output buffer (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23001 and fix it if it is affected.

What it is: CVE-2022-23001 is a medium-severity vulnerability in Western Digital Sweet B Library, published on 29 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23001 in the wild and no public exploit code.

Affected product: Western Digital Sweet B Library. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-23001/ (Markdown: https://insights.sbomify.com/CVE-2022-23001/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23001
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23001
- OSV: https://osv.dev/vulnerability/CVE-2022-23001

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-23001/
Summaries are generated and may contain mistakes; the official description above is the record.