# CVE-2023-50658: jose2go vulnerable to denial of service via large p2c value

> Attackers can cause denial of service via CPU exhaustion in the jose2go Go library by supplying a large PBES2 count value.

- **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:** Yes
- **Published:** 25 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-35422, AZL-35426, DEBIAN-CVE-2023-50658, GHSA-6294-6rgp-fr7r, GHSA-mhpq-9638-x6pw, GO-2023-2409, UBUNTU-CVE-2023-50658

## What is CVE-2023-50658?

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

### Official description

The jose2go component before 1.6.0 for Go allows attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count) value.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

5 open source packages ship an affected version, including github.com/dvsekhvalnov/jose2go. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/dvsekhvalnov/jose2go` | Go | All versions | 1.5.1-0.20231206184617-48ba0b76bc88 |
| `github.com/dvsekhvalnov/jose2go` | Go | All versions | 1.5.1-0.20231206184617-48ba0b76bc88 |
| `github.com/dvsekhvalnov/jose2go` | Go | All versions | 1.5.1-0.20231206184617-48ba0b76bc88 |
| `github.com/dvsekhvalnov/jose2go` | Go | All versions | 1.6.0 |
| `github.com/dvsekhvalnov/jose2go` | Go | All versions | 1.6.0 |

Products: Dvsekhvalnov Jose2go.

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

Upgrade github.com/dvsekhvalnov/jose2go to a fixed version for your release line: 1.5.1-0.20231206184617-48ba0b76bc88 or 1.6.0.

## Is CVE-2023-50658 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63811](https://insights.sbomify.com/CVE-2025-63811/): jose2go is vulnerable to a JWT bomb attack through its decode function (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50658 is a high-severity denial of service vulnerability in n/a, published on 25 Dec 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-50658 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/dvsekhvalnov/jose2go (Go): affected all versions; fixed in 1.5.1-0.20231206184617-48ba0b76bc88
- github.com/dvsekhvalnov/jose2go (Go): affected all versions; fixed in 1.5.1-0.20231206184617-48ba0b76bc88
- github.com/dvsekhvalnov/jose2go (Go): affected all versions; fixed in 1.5.1-0.20231206184617-48ba0b76bc88
- github.com/dvsekhvalnov/jose2go (Go): affected all versions; fixed in 1.6.0
- github.com/dvsekhvalnov/jose2go (Go): affected all versions; fixed in 1.6.0

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

## Sources

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

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