Usage of hard-coded Passport Secret

Overview

• Rule ID: javascript_third_parties_passport_hardcoded_secret

• Applicable Languages: Javascript

• Weakness ID: CWE-798

Description

Storing secrets directly in your code, such as a passport authentication secret, is insecure. This approach makes your application susceptible to attacks if the codebase is exposed.

Remediation Guidelines

• Avoid hard-coding secrets in your application code. Hard-coding makes sensitive information readily accessible to anyone who can view the code.

  const strategy = new GoogleStrategy({ clientSecret: 'your_hardcoded_secret' }); // unsafe
  passport.use(strategy);
  

• Use environment variables to manage secrets securely. This approach keeps sensitive information out of your codebase and makes it harder for unauthorized users to access.

  const strategy = new GoogleStrategy({ clientSecret: process.env.GOOGLE_SECRET });
  passport.use(strategy);
  

References

• OWASP hardcoded passwords

• CWE-798: Use of Hard-coded Credentials

• OWASP Top 10: A07:2021 - Identification and Authentication Failures

Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our SAST TOOL