CVE-2024-31209Public exploit

BEAM node crash via unbounded atom creation

Published Apr 4, 2024 · Updated Sep 3, 2024

Denial of service in oidcc affected 3.x releases allows local users with application control to crash a BEAM node through atom exhaustion. oidcc_provider_configuration_worker:get_ets_table_name/1 converts each worker-name atom to a list, appends "_table", and calls erlang:list_to_atom/1, permanently allocating a new atom for each distinct name. Exploitation requires repeated calls with different atom names—normally static application values—and filling the non-garbage-collected atom table crashes the hosting node; affected ranges are 3.0.0 through 3.0.1, 3.1.0 through 3.1.1, and 3.2.0-beta.1 through 3.2.0-beta.2.

CVSS severity5.3
Medium
EPSS probability0.24%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Denial of service in oidcc affected 3.x releases allows local users with application control to crash a BEAM node through atom exhaustion. oidcc_provider_configuration_worker:get_ets_table_name/1 converts each worker-name atom to a list, appends "_table", and calls erlang:list_to_atom/1, permanently allocating a new atom for each distinct name. Exploitation requires repeated calls with different atom names—normally static application values—and filling the non-garbage-collected atom table crashes the hosting node; affected ranges are 3.0.0 through 3.0.1, 3.1.0 through 3.1.1, and 3.2.0-beta.1 through 3.2.0-beta.2.

The record

CVE
CVE-2024-31209
Published
Apr 4, 2024
Updated
Sep 3, 2024
Vendor
Erlang Ecosystem Foundation
Product
oidcc
Classifications
CWE-400, T1499.004
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. Apr 4, 2024CVE publishedPublication date reported by the CVE source.
  2. Sep 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 3.0.0, < 3.0.2
  2. Affected versionversion=>= 3.1.0, < 3.1.2
  3. Affected versionversion=>= 3.2.0-beta.1, < 3.2.0-beta.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

Erlang Ecosystem Foundation · oidccversion=>= 3.0.0, < 3.0.2; version=>= 3.1.0, < 3.1.2; version=>= 3.2.0-beta.1, < 3.2.0-beta.3

Published CVSS scores

5.3GitHubCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-400Uncontrolled Resource Consumption
T1499.004Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo