Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/google/exposure-notifications-server

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedGoPublished

    Import of incorrectly embargoed keys could cause early publication

    GHSA-3wxm-m9m4-cprj

    Affected
    • Go github.com/google/exposure-notifications-server < 0.18.3; >= 0.19.0, < 0.19.2
    Fixed in
    0.19.20.18.3· Vendor fix available
    Issue
    Impact If your installation is using the export-importer service, there is potential impact. If your installation is not importing keys via the export-importer services, your installation is not impacted. In versions 0.19.1 and earlier, the export-importer service 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.3 and all versions 0.19.2 and 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 Open an issue in exposure-notifications-server Email us at exposure-notifications-feedback@google.com

    Recommended action: Upgrade to 0.19.2 or 0.18.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →