Allocation of Resources Without Limits or Throttling vulnerability in esaml_binding in dropbox...
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.
細工されたSAMLResponseを送り付けられることで、Erlang VMのアトムテーブルが枯渇し、ノードがクラッシュする可能性があります。認証前の処理で発生するため、認証は不要です。対象はesamlの0.1.0以降で、修正版は公開されていないため、最新の情報を確認してください。
Paquets affectés
| Écosystème | Paquet | Concernées | Corrigé |
|---|---|---|---|
| arekinath | esaml |
≥ deeb84378d5c82153b470e99d24f77c38afca14a (pas de correctif) |
— |
| handnot2 | esaml |
≥ deeb84378d5c82153b470e99d24f77c38afca14a (pas de correctif) |
— |
| dropbox | esaml |
≥ deeb84378d5c82153b470e99d24f77c38afca14a (pas de correctif) |
— |
| Hex | esaml |
≥ 0.1.0 (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_binding in dropbox esaml allows an unauthenticated attacker to exhaust the Erlang VM atom table and crash the node via a crafted SAMLResponse.
esaml_binding:decode_response/2 parses the decoded SAMLResponse with xmerl_scan:string/2, which interns every element name, attribute name, and namespace prefix it reads as a permanent atom. The SAML consume (ACS) and single-logout endpoints call it on unauthenticated requests before any signature check, so one well-formed document with thousands of distinct names mints thousands of atoms while staying inside the 128 KB request body limit. Atoms are never reclaimed and the VM caps the atom table at about one million entries, so a few dozen requests abort the node.
This issue affects esaml: from 0.1.0 onward.
Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory
Références
- package hex.pm
- web cna.erlef.org
- web osv.dev
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com