Skip to content

Insufficient Granularity of Access Control in github.com/google/exposure-notifications-verification-server

Moderate severity GitHub Reviewed Published Nov 9, 2021 in google/exposure-notifications-verification-server • Updated Jan 29, 2023

Package

gomod github.com/google/exposure-notifications-verification-server (Go)

Affected versions

< 1.1.2

Patched versions

1.1.2

Description

Impact

Users or API keys with permission to expire verification codes could have expired codes that belonged to another realm if they guessed the UUID.

Patches

v1.1.2+

Workarounds

There are no workarounds, and there are no indications this has been exploited in the wild. Verification codes can only be expired by providing their 64-bit UUID, and verification codes are already valid for a very short period of time (thus the UUID rotates frequently).

For more information

Contact [email protected]

References

@sethvargo sethvargo published to google/exposure-notifications-verification-server Nov 9, 2021
Reviewed Nov 9, 2021
Published to the GitHub Advisory Database Nov 10, 2021
Published by the National Vulnerability Database Dec 9, 2021
Last updated Jan 29, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

EPSS score

0.084%
(37th percentile)

Weaknesses

CVE ID

CVE-2021-22565

GHSA ID

GHSA-wx8q-rgfr-cf6v

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.