🛡️ Sentinel: [CRITICAL] Fix Insecure Production Defaults

[Magnopiro-oficial]

🛡️ Sentinel: [CRITICAL] Fix Insecure Production Defaults

🚨 Severity: CRITICAL
💡 Vulnerability: The backend configuration allowed the application to start in production mode (NODE_ENV=production) even if critical secrets like AWS keys, SMTP credentials, and KYC keys were missing. In this scenario, the application silently fell back to insecure default values (e.g., 'dev-access-key'), potentially exposing the application to unauthorized access or causing it to interact with incorrect environments.

🎯 Impact:

• Risk of using dummy/dev credentials in production.
• Potential silent failure of external services (AWS S3, Email, KYC) or misrouting of data.
• False sense of security assuming production env is correctly configured.

🔧 Fix:

• Updated backend/src/config/env.config.ts to include AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, SMTP_USER, SMTP_PASS, and KYC_API_KEY in the requiredProdVars list.
• The application now throws a hard error at startup if any of these variables are missing in production.

✅ Verification:

• Ran a reproduction script in backend/ verifying that NODE_ENV=production with missing keys now throws Error: Variável AWS_ACCESS_KEY_ID é obrigatória em produção.
• Verified that providing all keys allows the application to load the environment successfully.

---

PR created automatically by Jules for task 6295507681011721065 started by @Magnopiro-oficial

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.