Import of incorrectly embargoed keys could cause early publication
Moderate severity
GitHub Reviewed
Published
Apr 1, 2021
in
google/exposure-notifications-server
•
Updated Jan 9, 2023
Package
Affected versions
< 0.18.3
>= 0.19.0, < 0.19.2
Patched versions
0.18.3
0.19.2
Description
Reviewed
May 20, 2021
Published to the GitHub Advisory Database
May 21, 2021
Last updated
Jan 9, 2023
Impact
If your installation is using the
export-importerservice, there is potential impact.If your installation is not importing keys via the
export-importerservices, your installation is not impacted.In versions
0.19.1and earlier, theexport-importerservice assumed that the server it was importing from had properly embargoed keys for at least 2 hours after their expiry time. There are now known instances of servers that did not properly embargo keys.This could allow allow for imported keys to be re-published before they have expired, allowing for potential replay of RPIs.
Patches
This is patched in
v0.18.3and all versions0.19.2and later.Workarounds
Ensure that the servers you are importing export zip files from are not publishing keys too early.
References
n/a
For more information
If you have any questions or comments about this advisory
References