# CVE-2023-49292: Possible private key restoration in go package github.com/ecies/go

> An attacker can recover private keys by interacting with specific ECIES functions in the Go library, compromising encrypted data confidentiality.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-37343, AZL-37392, AZL-58246, AZL-78898, GHSA-8j98-cjfr-qx3h, GO-2023-2380

## What is CVE-2023-49292?

CVE-2023-49292 is a medium-severity vulnerability in ecies go, published on 4 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ecies is an Elliptic Curve Integrated Encryption Scheme for secp256k1 in Golang. If funcations Encapsulate(), Decapsulate() and ECDH() could be called by an attacker, they could recover any private key that interacts with it. This vulnerability was patched in 2.0.8. Users are advised to upgrade.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

3 open source packages ship an affected version, including github.com/ecies/go/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ecies/go/v2` | Go | All versions | 2.0.8 |
| `github.com/ecies/go/v2` | Go | All versions | 2.0.8 |
| `github.com/ecies/go/v2` | Go | All versions | 2.0.8 |

Products: Ecies Go.

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

Upgrade github.com/ecies/go/v2 to 2.0.8 or later.

## Is CVE-2023-49292 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-49292 is a medium-severity vulnerability in ecies go, published on 4 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-49292 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ecies/go/v2 (Go): affected all versions; fixed in 2.0.8
- github.com/ecies/go/v2 (Go): affected all versions; fixed in 2.0.8
- github.com/ecies/go/v2 (Go): affected all versions; fixed in 2.0.8

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

## Sources

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

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