GHSA-G636-Q5FC-4PR7

GHSA-G636-Q5FC-4PR7 is a low-severity security vulnerability in github.com/moov-io/customers (go), affecting versions < 0.5.0. It is fixed in 0.5.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

accounts: Hash account number using Salt

@alovak found that currently when we build hash of account number we do not "salt" it. Which makes it vulnerable to rainbow table attack.

What did you expect to see?
I expected salt (some random number from configuration) to be used in hash.AccountNumber

I would generate salt per tenant at least (maybe per organization).

Impact

Affected versions

github.com/moov-io/customers (< 0.5.0)

Security releases

github.com/moov-io/customers → 0.5.0 (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 environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade github.com/moov-io/customers to 0.5.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-G636-Q5FC-4PR7? GHSA-G636-Q5FC-4PR7 is a low-severity security vulnerability in github.com/moov-io/customers (go), affecting versions < 0.5.0. It is fixed in 0.5.0.
  2. Which versions of github.com/moov-io/customers are affected by GHSA-G636-Q5FC-4PR7? github.com/moov-io/customers (go) versions < 0.5.0 is affected.
  3. Is there a fix for GHSA-G636-Q5FC-4PR7? Yes. GHSA-G636-Q5FC-4PR7 is fixed in 0.5.0. Upgrade to this version or later.
  4. Is GHSA-G636-Q5FC-4PR7 exploitable, and should I be worried? Whether GHSA-G636-Q5FC-4PR7 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
  5. What actually determines whether GHSA-G636-Q5FC-4PR7 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.
  6. How do I fix GHSA-G636-Q5FC-4PR7? Upgrade github.com/moov-io/customers to 0.5.0 or later.

Stop the waste.
Protect your environment with Kodem.