| शीर्षक | SciPhi-AI R2R <=3.6.6 Hard-coded Credentials |
|---|
| विवरण | R2R signs and verifies HS256 session JWTs with R2R_SECRET_KEY. If that variable is unset or empty, both the bcrypt and NaCl crypto providers fall back to a secret hardcoded in the public source tree . Official Docker env files ship R2R_SECRET_KEY= empty, so default deployments use that constant. An unauthenticated attacker can mint a valid access token for any existing account, including the default superuser [email protected], and call authenticated APIs as that user. Enabling require_authentication does not fix this unless the secret is also changed. Password rotation does not invalidate tokens signed with the still-default HMAC key. |
|---|
| स्रोत | ⚠️ https://gist.github.com/DReazer/6bc4f88053ec35f8358395bcc0d1a0bb |
|---|
| उपयोगकर्ता | Snkn0w (UID 90071) |
|---|
| सबमिशन | 26/08/2026 05:56 AM (1 महीना पहले) |
|---|
| संयम | 03/10/2026 08:05 PM (1 month later) |
|---|
| स्थिति | स्वीकृत |
|---|
| VulDB प्रविष्टि | 413372 [SciPhi-AI R2R तक 3.6.6 JWT Secret DEFAULT_BCRYPT_SECRET_KEY/DEFAULT_NACL_SECRET_KEY कमजोर प्रमाणीकरण] |
|---|
| अंक | 20 |
|---|