What is GHSA-3WXM-M9M4-CPRJ?

GHSA-3WXM-M9M4-CPRJ is a medium-severity security vulnerability in github.com/google/exposure-notifications-server (go), affecting versions < 0.18.3. It is fixed in 0.18.3, 0.19.2.

Which versions of github.com/google/exposure-notifications-server are affected by GHSA-3WXM-M9M4-CPRJ?

github.com/google/exposure-notifications-server (go) versions < 0.18.3 is affected.

Is there a fix for GHSA-3WXM-M9M4-CPRJ?

Yes. GHSA-3WXM-M9M4-CPRJ is fixed in 0.18.3, 0.19.2. Upgrade to this version or later.

Is GHSA-3WXM-M9M4-CPRJ exploitable, and should I be worried?

Whether GHSA-3WXM-M9M4-CPRJ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-3WXM-M9M4-CPRJ is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-3WXM-M9M4-CPRJ?

Upgrade: github.com/google/exposure-notifications-server to 0.18.3 or later, github.com/google/exposure-notifications-server to 0.19.2 or later.

GHSA-3WXM-M9M4-CPRJ

Q: Which versions of github.com/google/exposure-notifications-server are affected by GHSA-3WXM-M9M4-CPRJ?

github.com/google/exposure-notifications-server (go) versions < 0.18.3 is affected.

Q: Is there a fix for GHSA-3WXM-M9M4-CPRJ?

Yes. GHSA-3WXM-M9M4-CPRJ is fixed in 0.18.3, 0.19.2. Upgrade to this version or later.

Q: Is GHSA-3WXM-M9M4-CPRJ exploitable, and should I be worried?

Whether GHSA-3WXM-M9M4-CPRJ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-3WXM-M9M4-CPRJ is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-3WXM-M9M4-CPRJ?

Upgrade: github.com/google/exposure-notifications-server to 0.18.3 or later, github.com/google/exposure-notifications-server to 0.19.2 or later.

Summary

Import of incorrectly embargoed keys could cause early publication

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]

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.

Affected versions

github.com/google/exposure-notifications-server (< 0.18.3) github.com/google/exposure-notifications-server (>= 0.19.0, < 0.19.2)

Security releases

github.com/google/exposure-notifications-server → 0.18.3 (go) github.com/google/exposure-notifications-server → 0.19.2 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

This is patched in v0.18.3 and all versions 0.19.2 and later.

Frequently Asked Questions

What is GHSA-3WXM-M9M4-CPRJ? GHSA-3WXM-M9M4-CPRJ is a medium-severity security vulnerability in github.com/google/exposure-notifications-server (go), affecting versions < 0.18.3. It is fixed in 0.18.3, 0.19.2.
Which versions of github.com/google/exposure-notifications-server are affected by GHSA-3WXM-M9M4-CPRJ? github.com/google/exposure-notifications-server (go) versions < 0.18.3 is affected.
Is there a fix for GHSA-3WXM-M9M4-CPRJ? Yes. GHSA-3WXM-M9M4-CPRJ is fixed in 0.18.3, 0.19.2. Upgrade to this version or later.
Is GHSA-3WXM-M9M4-CPRJ exploitable, and should I be worried? Whether GHSA-3WXM-M9M4-CPRJ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-3WXM-M9M4-CPRJ is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-3WXM-M9M4-CPRJ?
- Upgrade github.com/google/exposure-notifications-server to 0.18.3 or later
- Upgrade github.com/google/exposure-notifications-server to 0.19.2 or later