{"answers":{"affected":"2 open source packages ship an affected version, including github.com/moov-io/customers.","exploited":"There is no known exploitation of GHSA-g636-q5fc-4pr7 in the wild and no public exploit code.","fix":"Upgrade github.com/moov-io/customers to 0.5.0 or later.","what":"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."},"fix_prompt":"Check this codebase for GHSA-g636-q5fc-4pr7 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of GHSA-g636-q5fc-4pr7 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/moov-io/customers (Go): affected all versions; fixed in 0.5.0\n- github.com/moov-io/customers (Go): affected all versions; fixed in 0.5.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-g636-q5fc-4pr7/ (Markdown: https://insights.sbomify.com/GHSA-g636-q5fc-4pr7/index.md)","id":"GHSA-g636-q5fc-4pr7","markdown":"https://insights.sbomify.com/GHSA-g636-q5fc-4pr7/index.md","name":"GHSA-g636-q5fc-4pr7","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Go customer library","requires_auth":"none","summary":"Unsalted hashing of account numbers allows attackers to reverse hashes via rainbow tables, exposing sensitive customer data.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.\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).","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"accounts: Hash account number using Salt","id":"GHSA-g636-q5fc-4pr7","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"weak_cryptography","year":"2021"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"github.com/moov-io/customers","purl":null,"source":"GHSA-g636-q5fc-4pr7"},{"ecosystem":"Go","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"github.com/moov-io/customers","purl":"pkg:golang/github.com/moov-io/customers","source":"GHSA-g636-q5fc-4pr7"}],"products":null,"published":"2021-05-24","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Unsalted hashing of account numbers allows attackers to reverse hashes via rainbow tables, exposing sensitive customer data.","url":"https://insights.sbomify.com/GHSA-g636-q5fc-4pr7/"}