GHSA-3wxm-m9m4-cprj
GHSA-3wxm-m9m4-cprj is a security vulnerability in github.com/google/exposure-notifications-server. O3 Security confirms whether GHSA-3wxm-m9m4-cprj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Import of incorrectly embargoed keys could cause early publication
Real-World Exposure
github.com/google/exposure-notifications-server🐹github.com/google/exposure-notifications-serverReal-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
- Open an issue in exposure-notifications-server
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/google/exposure-notifications-server | all versions | 0.18.3 |
| 🐹Go | github.com/google/exposure-notifications-server | ≥ 0.19.0&&< 0.19.2 | 0.19.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/exposure-notifications-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
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.
How O3 protects you
O3 pinpoints whether GHSA-3wxm-m9m4-cprj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-3wxm-m9m4-cprj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-3wxm-m9m4-cprj in your dependencies?
O3 detects GHSA-3wxm-m9m4-cprj across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.