GHSA-g636-q5fc-4pr7: accounts Hash Account Number Using Salt Vulnerability

LOW
Published
Advisory Summary

GHSA-g636-q5fc-4pr7 is a LOW hash account number using salt vulnerability (General Security Weakness) affecting accounts libraries in the Go ecosystem. The issue involves hash account number using salt. Remediation is available by upgrading affected packages to version 0.5.0.

GHSA-g636-q5fc-4pr7 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-g636-q5fc-4pr7
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product accounts
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-g636-q5fc-4pr7

To remediate this vulnerability, upgrade all affected accounts dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/moov-io/customers fixed: 0.5.0
Upgrade github.com/moov-io/customers to 0.5.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/moov-io/customers

How to Check if You Are Affected

To determine whether your application is affected by GHSA-g636-q5fc-4pr7, inspect your project dependencies for accounts:

inspect dependencies for github.com/moov-io/customers

Analyze the terminal output to locate any version of accounts in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.5.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In accounts, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

GHSA-g636-q5fc-4pr7 Affected accounts Versions

1 component(s)
Fixed Versions:
0.5.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/moov-io/customers
Go
< 0.5.0
0.5.0

References

Frequently Asked Questions

What is GHSA-g636-q5fc-4pr7?
GHSA-g636-q5fc-4pr7 is a security vulnerability in accounts involving Hash account number using Salt under General Security Weakness.
Which accounts versions are affected?
Affected versions include releases prior to 0.5.0 across affected packages: github.com/moov-io/customers.
What version fixes GHSA-g636-q5fc-4pr7?
Upgrading to 0.5.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/moov-io/customers affected?
Yes, github.com/moov-io/customers is affected in releases prior to 0.5.0. Upgrade your dependency to 0.5.0 or later.
What CWE is associated with GHSA-g636-q5fc-4pr7?
GHSA-g636-q5fc-4pr7 is classified under General Security Weakness.
How can I check Go dependencies for GHSA-g636-q5fc-4pr7?
Run the dependency tree command: 'inspect dependencies for github.com/moov-io/customers'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g636-q5fc-4pr7",
  "modified" : "2021-05-21T22:11:53Z",
  "published" : "2021-05-24T17:00:27Z",
  "aliases" : [ ],
  "summary" : "accounts: Hash account number using Salt",
  "details" : "@alovak found that currently when we build hash of account number we do not \"salt\" it. Which makes it vulnerable to rainbow table attack.\n\n**What did you expect to see?**\nI 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)\n\nI would generate salt per tenant at least (maybe per organization).",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/moov-io/customers"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.5.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/moov-io/customers/security/advisories/GHSA-g636-q5fc-4pr7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-05-21T22:11:53Z",
    "nvd_published_at" : null
  }
}