An issue was discovered in NPMs package @evershop/evershop before version 1.0.0-rc.8. The HMAC secret used for generating tokens is hardcoded as secret. A weak HMAC secret poses a risk because attackers can use the predictable secret to create valid JSON Web Tokens (JWTs), allowing them access to important information and actions within the application.
Weakness
The product contains hard-coded credentials, such as a password or cryptographic key.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Evershop |
Evershop |
1.0.0-beta (including) |
1.0.0-beta (including) |
| Evershop |
Evershop |
1.0.0-beta1 (including) |
1.0.0-beta1 (including) |
| Evershop |
Evershop |
1.0.0-beta2 (including) |
1.0.0-beta2 (including) |
| Evershop |
Evershop |
1.0.0-beta3 (including) |
1.0.0-beta3 (including) |
| Evershop |
Evershop |
1.0.0-beta4 (including) |
1.0.0-beta4 (including) |
| Evershop |
Evershop |
1.0.0-beta5 (including) |
1.0.0-beta5 (including) |
| Evershop |
Evershop |
1.0.0-rc1 (including) |
1.0.0-rc1 (including) |
| Evershop |
Evershop |
1.0.0-rc2 (including) |
1.0.0-rc2 (including) |
| Evershop |
Evershop |
1.0.0-rc3 (including) |
1.0.0-rc3 (including) |
| Evershop |
Evershop |
1.0.0-rc5 (including) |
1.0.0-rc5 (including) |
| Evershop |
Evershop |
1.0.0-rc6 (including) |
1.0.0-rc6 (including) |
| Evershop |
Evershop |
1.0.0-rc7 (including) |
1.0.0-rc7 (including) |
Extended Description
There are two main variations:
Potential Mitigations
- For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible [REF-7].
- In Windows environments, the Encrypted File System (EFS) may provide some protection.
- For inbound authentication using passwords: apply strong one-way hashes to passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When handling an incoming password during authentication, take the hash of the password and compare it to the saved hash.
- Use randomly assigned salts for each separate hash that is generated. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
- For front-end to back-end connections: Three solutions are possible, although none are complete.
References