Security readout for executives and security teams
Plain-English summary
This flaw could let an attacker make a patient’s verification code expire before the patient uses it. The business impact is reduced effectiveness of exposure notification workflows: valid patients may be blocked from uploading keys needed to alert exposed contacts.
Executive priority
Handle as a moderate public-health service integrity issue. It is not described as data theft or full compromise, but it can disrupt exposure notifications by preventing legitimate patient uploads.
Technical view
CVE-2021-22565 is an access-control weakness in Google Exposure Notifications Verification Server. The CVSS vector indicates network access, low complexity, no privileges, and no user interaction, with low integrity and availability impact. Google recommended upgrading to version 1.1.2 or later.
Likely exposure
Exposure is limited to organizations operating Google Exposure-notifications-verification-server versions before the recommended 1.1.2 release. The source bundle does not identify specific affected version ranges beyond unspecified vulnerable versions.
Exploitation context
The CVE describes premature expiration of verification codes. The source bundle does not cite active exploitation, and KEV status is false. Treat exploitation as possible based on the vulnerability description, but not confirmed in the provided evidence.
Researcher notes
Evidence supports CWE-284 insufficient access control, CVSS 6.5, and vendor remediation by upgrade. The provided sources do not include detailed affected ranges, proof of exploitation, or alternative mitigations.
Mitigation direction
- Upgrade Exposure Notifications Verification Server to v1.1.2 or later.
- Review the GitHub advisory and release notes for deployment-specific guidance.
- Prioritize internet-accessible verification server deployments.
- Check vendor guidance before applying compensating controls not named in sources.
Validation and detection
- Inventory any Google Exposure Notifications Verification Server deployments.
- Confirm deployed versions are v1.1.2 or newer.
- Verify verification-code expiration behavior against vendor guidance.
- Review operational metrics for abnormal code-expiration failures.
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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-22565 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:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/google/exposure-notifications-verification-server/security/advisories/GHSA-wx8q-rgfr-cf6vCVE reference · x_refsource_MISC
- https://github.com/google/exposure-notifications-verification-server/releases/tag/v1.1.2CVE 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.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.