# OSV-2023-1115: Use-of-uninitialized-value in fp_uninit

> An attacker can cause a denial of service in the libecc library by triggering a use-of-uninitialized-value error during ECC public key validation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Nov 2023

## What is OSV-2023-1115?

OSV-2023-1115 is a vulnerability in libecc, published on 5 Nov 2023. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63867

```
Crash type: Use-of-uninitialized-value
Crash state:
fp_uninit
cryptofuzz::module::libecc::OpECC_ValidatePubkey
cryptofuzz::ExecutorBase<bool, cryptofuzz::operation::ECC_ValidatePubkey>::callM
```

## Which versions are affected by OSV-2023-1115?

1 open source package ship an affected version, including libecc.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libecc` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2023-1115?

No fix has been published for OSV-2023-1115 yet. Limit exposure of the affected software until one is available.

## Is OSV-2023-1115 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2023-1115 and fix it if it is affected.

What it is: OSV-2023-1115 is a vulnerability in libecc, published on 5 Nov 2023. 
Exploitation: There is no known exploitation of OSV-2023-1115 in the wild and no public exploit code.

Affected packages and fixed versions:
- libecc (OSS-Fuzz): affected all versions; no fix listed

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

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2023-1115

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