GHSA-56r6-ccm5-8hg3 json
Alchemy Non-SMA and Webauthn Account Security Advisory
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
### Impact A potential security issue has been mitigated on old account deployment functions from the factory. Smart wallets in use on all existing supported networks are not impacted. ### Patches Please direct creation of new wallets to either `createSemiModularAccount` on `AccountFactory.sol` or `createWebAuthnAccount` on `WebAuthnFactory.sol`.
Patch / fix
- npm @account-kit/smart-contracts 4.52.0
Is GHSA-56r6-ccm5-8hg3 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.42.0, <4.52.0 |
4.52.0 |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/alchemyplatform/aa-sdk/commit/b343437a9e4a833c25fed7bc8785a815cbbae0ee
web
-
github.com
/alchemyplatform/modular-account/commit/2352c9b692935ba97d98619cb31ba1653eee241f
web
-
github.com
/alchemyplatform/modular-account/security/advisories/GHSA-56r6-ccm5-8hg3
web
-
github.com
/alchemyplatform/modular-account
package
Sources
- GitHub Advisory GHSA-56r6-ccm5-8hg3
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.