Invia #947748: SciPhi-AI R2R <=3.6.6 Hard-coded Credentialsinformazioni

TitoloSciPhi-AI R2R <=3.6.6 Hard-coded Credentials
DescrizioneR2R 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.
Fonte⚠️ https://gist.github.com/DReazer/6bc4f88053ec35f8358395bcc0d1a0bb
Utente
 Snkn0w (UID 90071)
Sottomissione26/08/2026 05:56 (1 mese fa)
Moderazione03/10/2026 20:05 (1 month later)
StatoAccettato
Voce VulDB413372 [SciPhi-AI R2R fino a 3.6.6 JWT Secret DEFAULT_BCRYPT_SECRET_KEY/DEFAULT_NACL_SECRET_KEY autenticazione debole]
Punti20

Do you want to use VulDB in your project?

Use the official API to access entries easily!