# CVE-2024-31209: OpenID Connect client Atom Exhaustion in provider configuration worker ets table location

> Attackers can cause denial of service in Erlang applications using the oidcc library by exhausting atoms via specific worker function calls.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Apr 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-mj35-2rgf-cv8p

## What is CVE-2024-31209?

CVE-2024-31209 is a medium-severity denial of service vulnerability in erlef oidcc, published on 4 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

oidcc is the OpenID Connect client library for Erlang. Denial of Service (DoS) by Atom exhaustion is possible by calling `oidcc_provider_configuration_worker:get_provider_configuration/1` or `oidcc_provider_configuration_worker:get_jwks/1`. This issue has been patched in version(s)`3.1.2` & `3.2.0-beta.3`.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2024-31209?

6 open source packages ship an affected version, including oidcc.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oidcc` | Hex | From 3.0.0 | 3.0.2 |
| `oidcc` | Hex | From 3.0.0 | 3.0.2 |
| `oidcc` | Hex | From 3.1.0 | 3.1.2 |
| `oidcc` | Hex | From 3.1.0 | 3.1.2 |
| `oidcc` | Hex | From 3.2.0-beta.1 | 3.2.0-beta.3 |
| `oidcc` | Hex | From 3.2.0-beta.1 | 3.2.0-beta.3 |

## How do I fix CVE-2024-31209?

Upgrade oidcc to a fixed version for your release line: 3.0.2, 3.1.2 or 3.2.0-beta.3.

## Is CVE-2024-31209 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31209 and fix it if it is affected.

What it is: CVE-2024-31209 is a medium-severity denial of service vulnerability in erlef oidcc, published on 4 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-31209 in the wild and no public exploit code.

Affected packages and fixed versions:
- oidcc (Hex): affected from 3.0.0; fixed in 3.0.2
- oidcc (Hex): affected from 3.0.0; fixed in 3.0.2
- oidcc (Hex): affected from 3.1.0; fixed in 3.1.2
- oidcc (Hex): affected from 3.1.0; fixed in 3.1.2
- oidcc (Hex): affected from 3.2.0-beta.1; fixed in 3.2.0-beta.3
- oidcc (Hex): affected from 3.2.0-beta.1; fixed in 3.2.0-beta.3

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

## Sources

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

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