Security readout for executives and security teams
Plain-English summary
CVE-2021-22548 is a memory-handling flaw in Google Asylo enclave code. A low-privileged local attacker may be able to cause trusted enclave memory to be copied and later exposed. The main business concern is disclosure of sensitive data intended to remain protected inside the enclave.
Executive priority
Treat this as a targeted moderate-priority issue. It is not flagged as exploited, but it can undermine enclave confidentiality where Asylo protects sensitive data. Patch affected enclave workloads during the next security maintenance window, sooner for high-value secrets.
Technical view
The issue affects Asylo TrustedPrimitives::UntrustedCall. The source describes attacker-controlled pointer manipulation from untrusted memory toward trusted memory, leading to trusted-region memory copying and potential later disclosure. CVSS 3.1 is 6.5 with local access, high complexity, low privileges, high confidentiality and integrity impact, and low availability impact.
Likely exposure
Exposure is likely limited to environments using Google Asylo, especially versions at or before 0.6.2 or code missing the referenced fix. The CVE record does not define precise affected version ranges beyond the update recommendation, so inventory validation is required.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. Exploitation requires local access, low privileges, and high attack complexity. This is not described as remotely exploitable, but enclave workloads handling sensitive data should treat it seriously.
Researcher notes
Evidence is sparse: the CVE record names Asylo and one fixing commit but does not provide detailed version ranges, exploit telemetry, or operational mitigations. Validation should focus on source or dependency provenance and whether the fix commit is present.
Mitigation direction
- Update Asylo past version 0.6.2, per the CVE recommendation.
- Apply or verify inclusion of Google Asylo commit 53ed5d8fd8118ced1466e509606dd2f473707a5c.
- Check current Google Asylo vendor guidance for supported remediation details.
- Limit local access to systems running affected enclave workloads until fixed.
- Prioritize workloads where enclave memory may contain secrets or regulated data.
Validation and detection
- Inventory applications and services that embed or depend on Google Asylo.
- Confirm the deployed Asylo version is later than 0.6.2 or includes the referenced commit.
- Review build manifests, vendored source, and container images for older Asylo code.
- Identify enclave workflows using TrustedPrimitives::UntrustedCall.
- Record compensating controls if patching cannot be completed immediately.
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.
CWE-788: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-22548 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
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L15.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/google/asylo/commit/53ed5d8fd8118ced1466e509606dd2f473707a5cCVE 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.
Access of Memory Location After End of Buffer
Access of Memory Location After End of Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.