# CVE-2023-24533: Incorrect multiplication of unreduced P-256 scalars in filippo.io/nistec

> Incorrect scalar multiplication in the Go NIST elliptic curve library may produce wrong results, though no known attacks exist.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Mar 2023
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-f6hc-9g49-xmx7, GO-2023-1595

## What is CVE-2023-24533?

CVE-2023-24533 is a high-severity vulnerability in filippo.io/nistec, published on 8 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiplication of certain unreduced P-256 scalars produce incorrect results. There are no protocols known at this time that can be attacked due to this.

Weakness: CWE-682 (Incorrect Calculation)

## Which versions are affected by CVE-2023-24533?

3 open source packages ship an affected version, including filippo.io/nistec. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `filippo.io/nistec` | Go | All versions | 0.0.2 |
| `filippo.io/nistec` | Go | All versions | 0.0.2 |
| `filippo.io/nistec` | Go | All versions | 0.0.2 |

Products: Nistec Project Nistec.

## How do I fix CVE-2023-24533?

Upgrade filippo.io/nistec to 0.0.2 or later.

## Is CVE-2023-24533 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24533 and fix it if it is affected.

What it is: CVE-2023-24533 is a high-severity vulnerability in filippo.io/nistec, published on 8 Mar 2023. 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-2023-24533 in the wild and no public exploit code.

Affected packages and fixed versions:
- filippo.io/nistec (Go): affected all versions; fixed in 0.0.2
- filippo.io/nistec (Go): affected all versions; fixed in 0.0.2
- filippo.io/nistec (Go): affected all versions; fixed in 0.0.2

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-2023-24533/ (Markdown: https://insights.sbomify.com/CVE-2023-24533/index.md)
```

## Sources

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

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