GHSA-g636-q5fc-4pr7 accounts: Hash account number using Salt

Not scored Published

Unsalted hashing of account numbers allows attackers to reverse hashes via rainbow tables, exposing sensitive customer data.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is GHSA-g636-q5fc-4pr7?

GHSA-g636-q5fc-4pr7 is a vulnerability in github.com/moov-io/customers, published on 24 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

@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).

Which versions are affected by GHSA-g636-q5fc-4pr7?

2 open source packages ship an affected version, including github.com/moov-io/customers.

PackageAffectedFixed in
github.com/moov-io/customers GoAll versions0.5.0
github.com/moov-io/customers GoAll versions0.5.0

How do I fix GHSA-g636-q5fc-4pr7?

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

Is GHSA-g636-q5fc-4pr7 being exploited?

There is no known exploitation of GHSA-g636-q5fc-4pr7 in the wild and no public exploit code.

Sources

Is GHSA-g636-q5fc-4pr7 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free