Do not use hardcoded secret with a JWT

Docs > Code Analysis > Static Analysis Rules > Do not use hardcoded secret with a JWT

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Metadata

ID: javascript-node-security/jwt-hardcoded-secret

Language: JavaScript

Severity: Error

Category: Security

CWE: 798

Description

Never hardcode secrets. Instead, use secrets from environment variables or a secret vault.

Non-Compliant Code Examples

var jwt = require("jsonwebtoken");

var token = jwt.sign({ foo: "bar" }, "secret");

var token = jwt.sign({ foo: "bar" }, 'secret');

var token = jwt.sign({ foo: "bar" }, `secret`);

Compliant Code Examples

var jwt = require("jsonwebtoken");

  var token = jwt.sign({ foo: "bar" }, process.env.JWT_SECRET);

How to use this rule

1
2
rulesets:
  - javascript-node-security     # Rules to enforce JavaScript node security.

Create a static-analysis.datadog.yml with the content above at the root of your repository
Use our free IDE Plugins or add Code Analysis scans to your CI pipelines
Get feedback on your code

For more information, please read the Code Analysis documentation

VS Code Extension

Identify code vulnerabilities directly in your
VS Code editor

JetBrains Plugin

Identify code vulnerabilities directly in
JetBrains products