How severe is GHSA-g636-q5fc-4pr7?

No CVSS score has been assigned to GHSA-g636-q5fc-4pr7 yet. Review the advisory details and affected package list to assess your exposure.

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

GHSA-g636-q5fc-4pr7 affects the following packages: github.com/moov-io/customers (Go). Ecosystems affected: Go.

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

Update github.com/moov-io/customers to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g636-q5fc-4pr7 is resolved across your whole dependency graph.

How do I detect GHSA-g636-q5fc-4pr7 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/moov-io/customers. 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.

How do I mitigate GHSA-g636-q5fc-4pr7 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-g636-q5fc-4pr7?

O3 pinpoints whether GHSA-g636-q5fc-4pr7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-g636-q5fc-4pr7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g636-q5fc-4pr7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-g636-q5fc-4pr7 published, and has it been updated?

GHSA-g636-q5fc-4pr7 was published on May 24, 2021 and was last updated on May 21, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-g636-q5fc-4pr7

GHSA-g636-q5fc-4pr7 is a security vulnerability in github.com/moov-io/customers. O3 Security confirms whether GHSA-g636-q5fc-4pr7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

accounts: Hash account number using Salt

Published

May 24, 2021

Updated

May 21, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 21, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/moov-io/customers

Real-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

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/moov-io/customers`	all versions	0.5.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/moov-io/customers. 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/moov-io/customers to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g636-q5fc-4pr7 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-g636-q5fc-4pr7 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-g636-q5fc-4pr7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

@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](https://github.com/moov-io/customers/blob/master/pkg/secrets/hash/account_number.go#L13) I would generate salt per tenant at least (maybe per organization).

O3 Security · Impact-Aware SCA

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

O3 detects GHSA-g636-q5fc-4pr7 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works