GHSA-g636-q5fc-4pr7
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).
What each source reports
GitHub AdvisoriesNo score
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).
- Record
GHSA-g636-q5fc-4pr7- Updated
- 2026-11-02
OSVNo score
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).
- Record
GHSA-g636-q5fc-4pr7- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/moov-io/customersGo | before 0.5.0 | 0.5.0 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-g636-q5fc-4pr7 is a vulnerability with no CVSS score yet in github.com/moov-io/customers, published May 24, 2021. No source lists public exploit code. Fixed in github.com/moov-io/customers 0.5.0.