Commit 65c42e8
committed
fix: validate JWT_SECRET env var before use in IP hashing
Both check-duplicate-login.js and track-session.js use
process.env.JWT_SECRET directly in hashIP() without validation.
If JWT_SECRET is unset, crypto.createHash silently hashes with
the literal string "undefined", producing deterministic but
incorrect hashes that degrade IP-based security checks.
Extract JWT_SECRET to a module-level constant with a validation
guard, consistent with all other API files in the project
(login.js, verify.js, reset-password.js, etc.).1 parent 707ae28 commit 65c42e8
2 files changed
+12
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
4 | 9 | | |
5 | 10 | | |
6 | 11 | | |
| |||
15 | 20 | | |
16 | 21 | | |
17 | 22 | | |
18 | | - | |
| 23 | + | |
19 | 24 | | |
20 | 25 | | |
21 | 26 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5 | 5 | | |
6 | 6 | | |
7 | 7 | | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
8 | 13 | | |
9 | 14 | | |
10 | 15 | | |
| |||
38 | 43 | | |
39 | 44 | | |
40 | 45 | | |
41 | | - | |
| 46 | + | |
42 | 47 | | |
43 | 48 | | |
44 | 49 | | |
| |||
0 commit comments