GHSA-wfm2-rq5g-f8v5 json
@account-kit/smart-contracts Allowlist Module Bypass Vulnerability
published last yr. modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Summary Allowlist module contains a bypass vulnerability
### Details The logic for using an allowlist on a Modular Account V2 contained a bug that allowed session keys to bypass any allowlist configuration
### Action If you are using @aa-sdk and/or @account-kit/smart-contracts between the versions of >=4.8.0 and <4.28.1, please upgrade to 4.28.2
Patch / fix
Is GHSA-wfm2-rq5g-f8v5 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @account-kit/smart-contracts | >=4.8.0, <4.28.2 |
4.28.2 |
Classification
- Weakness
-
- CWE-288 Authentication Bypass Using an Alternate Path or Channel
References
Sources
- GitHub Advisory GHSA-wfm2-rq5g-f8v5
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.