Security readout for executives and security teams
Plain-English summary
SKALE sgxwallet 1.58.3 had a buffer overflow in an encryption-related enclave function. The reported impact is a crash and compromised enclave. Public data confirms the issue was resolved before v1.77.0 and was not reproducible in v1.77.0, but gives limited detail on affected ranges or real-world attacks.
Executive priority
Prioritize if SKALE sgxwallet is used in systems protecting sensitive keys or enclave-backed operations. Otherwise, confirm exposure first because public severity and affected-range data are incomplete.
Technical view
The issue is an out-of-bounds write in sgx_disp_ippsAES_GCMEncrypt in SKALE sgxwallet 1.58.3. The CVE describes a segfault and compromised enclave. No CVSS, CWE, or precise affected version range is provided beyond 1.58.3 and the statement that it was fixed before v1.77.0.
Likely exposure
Exposure is most likely limited to environments running SKALE sgxwallet 1.58.3. Earlier or intermediate versions may need review, but the public source bundle does not define a full affected range.
Exploitation context
The source bundle does not report active exploitation, public weaponization, or KEV listing. Treat exploitation status as unconfirmed, not absent.
Researcher notes
Evidence is sparse: the CVE names one vulnerable version, one function, and a fix state before v1.77.0. Avoid broad affected-version claims unless confirmed by SKALE release or commit review.
Mitigation direction
- Inventory SKALE sgxwallet deployments and versions.
- Upgrade affected deployments to v1.77.0 or a later vendor-supported release.
- Review the referenced fix commit and release history.
- Check vendor guidance before relying on undocumented workarounds.
Validation and detection
- Confirm no production deployment runs sgxwallet 1.58.3.
- Verify upgraded systems report v1.77.0 or later.
- Review build artifacts for the referenced fix commit where applicable.
- Monitor logs for enclave crashes tied to sgxwallet encryption paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-36218 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/skalenetwork/sgxwallet/releasesCVE reference · x_refsource_MISC
- https://github.com/skalenetwork/sgxwallet/commit/77425c862ad20cd270d42c54f3d63e1eb4e02195CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
