Allocation of Resources Without Limits or Throttling vulnerability in esaml in dropbox esaml...
Résumé IA
Rédigé par une IA externe ; il peut contenir des erreurs. Vérifiez la description d'origine et les références ci-dessous avant d'agir.
esamlには、認証なしの攻撃者が未署名のLogoutResponseを大量に送ることで、Erlang VMのアトムテーブルを使い切りノードをクラッシュさせる問題があります。影響を受けるのは0.1.0以降のesamlです。修正版は提供されていないため、最新の情報を確認してください。
Paquets affectés
| Écosystème | Paquet | Concernées | Corrigé |
|---|---|---|---|
| Hex | esaml |
≥ 0.1.0 (pas de correctif) |
— |
| handnot2 | esaml |
≥ be692b56245071899757afa7ef47e43593d3de96 (pas de correctif) |
— |
| arekinath | esaml |
≥ be692b56245071899757afa7ef47e43593d3de96 (pas de correctif) |
— |
| dropbox | esaml |
≥ be692b56245071899757afa7ef47e43593d3de96 (pas de correctif) |
— |
Description d'origine La description telle que publiée par la source (souvent en anglais).
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
Références
- 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