# CVE-2023-36199: Null dereference in n/a

> An attacker can cause a denial of service in the skalenetwork sgxwallet library via the trustedGenerateEcdsaKey component.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2023
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-xc9v-4mxj-7qph

## What is CVE-2023-36199?

CVE-2023-36199 is a high-severity vulnerability in n/a, published on 25 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in skalenetwork sgxwallet v.1.9.0 and below allows an attacker to cause a denial of service via the trustedGenerateEcdsaKey component.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Skale Sgxwallet.

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

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

## Is CVE-2023-36199 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36199 exists.

## Other vulnerabilities in n/a

- [CVE-2021-36219](https://insights.sbomify.com/CVE-2021-36219/): Use after free in n/a (critical 9.8)
- [CVE-2023-36198](https://insights.sbomify.com/CVE-2023-36198/): Memory corruption in n/a (high 7.5)
- [CVE-2021-36218](https://insights.sbomify.com/CVE-2021-36218/): An issue was discovered in SKALE sgxwallet 1.58.3. (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-36199 is a high-severity vulnerability in n/a, published on 25 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36199 exists.

Affected product: n/a. 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-2023-36199/ (Markdown: https://insights.sbomify.com/CVE-2023-36199/index.md)
```

## Sources

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

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