esamlで未署名のLogoutResponseからerlang VMが停止される
Summary
esamlには、認証なしの攻撃者が未署名のLogoutResponseを大量に送ることで、Erlang VMのアトムテーブルを使い切りノードをクラッシュさせる問題があります。影響を受けるのは0.1.0以降のesamlです。修正版は提供されていないため、最新の情報を確認してください。
AI summary
Written by an external AI model and may contain mistakes. Check the original description and references below before acting on it.
esamlには、認証なしの攻撃者が未署名のLogoutResponseを大量に送ることで、Erlang VMのアトムテーブルを使い切りノードをクラッシュさせる問題があります。影響を受けるのは0.1.0以降のesamlです。修正版は提供されていないため、最新の情報を確認してください。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Hex | esaml |
≥ 0.1.0 (no fix yet) |
— |
| handnot2 | esaml |
≥ be692b56245071899757afa7ef47e43593d3de96 (no fix yet) |
— |
| arekinath | esaml |
≥ be692b56245071899757afa7ef47e43593d3de96 (no fix yet) |
— |
| dropbox | esaml |
≥ be692b56245071899757afa7ef47e43593d3de96 (no fix yet) |
— |
Original description The description as published by the source.
Allocation of Resources Without Limits or Throttling vulnerability in esaml in dropbox esaml allows an unauthenticated attacker to exhaust the Erlang VM atom table and crash the node via unsigned LogoutResponse messages.
esaml:status_code_map/1 in src/esaml.erl maps any StatusCode value it does not recognize to an atom with list_to_atom/1 on the last colon-separated segment of the URN. esaml_sp:validate_logout_response/2 verifies a signature only when the message carries one, so an unsigned LogoutResponse posted to the single-logout endpoint reaches esaml:decode_logout_response/1 and mints one permanent atom per distinct status value. Atoms are never reclaimed and the VM caps the atom table at about one million entries, so an attacker who posts that many distinct values aborts the node.
This issue affects esaml: from 0.1.0 onward.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
References
- package hex.pm
- web cna.erlef.org
- web github.com
- web github.com
- web github.com
- web osv.dev
- web nvd.nist.gov
- web github.com