github.com/moov-io/customers
View on Github
Activity
- Latest release
- 5y ago
- Total releases
- 20
- Cadence
- ~4 days
- Last 12 months
- 0
Reach
- Stars
- —
Details
- First release
- Jul 16, 2020
| Version | Released | |
|---|---|---|
v0.5.2
patch
|
v0.5.2
patch
Dependencies (26)
+ 18 more |
|
v0.5.1
patch
|
v0.5.1
patch
Dependencies (26)
+ 18 more |
|
v0.6.0-dev6
pre
|
v0.6.0-dev6
pre
Dependencies (26)
+ 18 more |
|
v0.6.0-dev5
pre
|
v0.6.0-dev5
pre
Dependencies (26)
+ 18 more |
|
v0.6.0-dev4
pre
|
v0.6.0-dev4
pre
Dependencies (26)
+ 18 more |
|
v0.6.0-dev3
pre
|
v0.6.0-dev3
pre
Dependencies (26)
+ 18 more |
|
v0.6.0-dev2
pre
|
v0.6.0-dev2
pre
Dependencies (26)
+ 18 more |
|
v0.6.0-dev1
pre
|
v0.6.0-dev1
pre
Dependencies (26)
+ 18 more |
|
v0.5.0
minor
|
v0.5.0
minor
Dependencies (26)
+ 18 more |
|
v0.5.0-dev23
pre
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.5.0-dev23
pre
Dependencies (27)
+ 19 more |
|
v0.5.0-dev21
pre
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.5.0-dev21
pre
Dependencies (27)
+ 19 more |
|
v0.5.0-dev10
pre
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.5.0-dev10
pre
Dependencies (27)
+ 19 more |
|
v0.5.0-dev4
pre
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.5.0-dev4
pre
Dependencies (27)
+ 19 more |
|
v0.5.0-dev2
pre
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.5.0-dev2
pre
Dependencies (26)
+ 18 more |
|
v0.5.0-dev1
pre
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.5.0-dev1
pre
Dependencies (26)
+ 18 more |
|
v0.5.0-rc4
pre
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.5.0-rc4
pre
Dependencies (25)
+ 17 more |
|
v0.5.0-rc3
pre
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.5.0-rc3
pre
Dependencies (20)
+ 12 more |
|
v0.5.0-rc2
pre
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.5.0-rc2
pre
Dependencies (20)
+ 12 more |
|
v0.5.0-rc1
pre
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.5.0-rc1
pre
Dependencies (20)
+ 12 more |
|
v0.4.1
initial
1 CVE
GHSA-g636-q5fc-4pr7
May 24, 2021
accounts: Hash account number using Salt
Low
@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). Fixed in
0.5.0
Updated May 21, 2021 · Source: OSV.dev |
v0.4.1
initial
Dependencies (19)
+ 11 more |