# CVE-2023-50966: erlang-jose vulnerable to denial of service via large p2c value

> Attackers can cause denial of service via high CPU consumption by sending a large PBES2 Count value in JOSE headers.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-39719, AZL-39857, DEBIAN-CVE-2023-50966, GHSA-9mg4-v392-8j68, UBUNTU-CVE-2023-50966

## What is CVE-2023-50966?

CVE-2023-50966 is a medium-severity denial of service vulnerability in n/a, published on 19 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

erlang-jose (aka JOSE for Erlang and Elixir) through 1.11.6 allow attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count) value in a JOSE header.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including jose.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jose` | Hex | All versions | 1.11.7 |
| `jose` | Hex | All versions | 1.11.7 |

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

Upgrade jose to 1.11.7 or later.

## Is CVE-2023-50966 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50966 is a medium-severity denial of service vulnerability in n/a, published on 19 Mar 2024. 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-50966 exists.

Affected packages and fixed versions:
- jose (Hex): affected all versions; fixed in 1.11.7
- jose (Hex): affected all versions; fixed in 1.11.7

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

## Sources

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

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