Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

Import of incorrectly embargoed keys could cause early publicationGHSA-3wxm-m9m4-cprj

GHSA-3wxm-m9m4-cprj is a security vulnerability in github.com/google/exposure-notifications-server. A fix is available for github.com/google/exposure-notifications-server — see the affected versions and patch details below.

Also known asGO-2022-0381
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Aug 21, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐹github.com/google/exposure-notifications-server🐹github.com/google/exposure-notifications-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/google/exposure-notifications-serverall versions0.18.3go get github.com/google/exposure-notifications-server@v0.18.3
🐹Gogithub.com/google/exposure-notifications-server≥ 0.19.0&&< 0.19.20.19.2go get github.com/google/exposure-notifications-server@v0.19.2

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/exposure-notifications-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/google/exposure-notifications-server to 0.18.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3wxm-m9m4-cprj is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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
O3 Security · Impact-Aware SCA

Is GHSA-3wxm-m9m4-cprj in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Import of incorrectly embargoed keys could cause early…