CVE-2026-54894— Atom-table exhaustion denial of service in Guardian via unbounded atom creation from binary keys

Atom-table exhaustion denial of service in Guardian via unbounded atom creation from binary keys

Allocation of Resources Without Limits or Throttling in ueberauth guardian allows denial of service via unbounded atom creation from attacker-influenced binary input. Guardian.Plug.Keys derives connection and session namespace keys by passing arbitrary binaries to String.to_atom/1. base_key/1 in lib/guardian/plug/keys.ex converts any binary into the atom :"guardian_<input>", and the derived helpers claims_key/1, resource_key/1, and token_key/1 create a second atom on top of that. key_from_other/1 likewise converts a regex-captured binary through String.to_atom/1. The public specs advertise String.t() as a valid argument, so passing a string is documented usage, and higher-level entry points such as Guardian.Plug.current_token(conn, key: key) thread the caller-supplied key straight into these functions. String.to_atom/1 creates a brand-new atom for every previously unseen binary, atoms are never garbage collected, and the BEAM atom table is fixed at roughly 1,048,576 entries by default. An application that routes attacker-influenced data (a tenant identifier, header, or other request input) into a Guardian key therefore mints one permanent atom per distinct value. A modest stream of varied, unauthenticated input permanently consumes the atom table and crashes the BEAM node, taking down every application running on it. This issue affects guardian: from 0.1.0 before 2.4.1.

CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H

不加限制或调节的资源分配

ueberauth Guardian 资源管理错误漏洞

ueberauth Guardian是ueberauth组织开源的一个基于令牌的身份验证库，可用于 Elixir 应用程序。 ueberauth Guardian 0.1.0至2.4.1之前版本存在资源管理错误漏洞，该漏洞源于资源分配无限制或节流，攻击者可控的二进制输入通过String.to_atom/1转换为原子，导致无限创建原子并耗尽BEAM原子表，可能造成拒绝服务。

N/A

N/A