eslint-plugin-lambda-security

🔐 Security-focused ESLint plugin for AWS Lambda and serverless applications. Detects hardcoded credentials, permissive CORS, environment secrets, and logging issues with AI-optimized fix guidance.

Serverless-first security: This plugin provides security rules for AWS Lambda, Middy.js, Serverless Framework, AWS SAM, and AWS SDK v3. With 5 security rules mapped to OWASP Serverless Top 10, CWE and CVSS, it transforms your linter into a serverless security auditor that AI assistants can understand and fix.

💡 What you get

• Serverless-focused coverage: 5 rules targeting Lambda-specific vulnerabilities (credentials, CORS, secrets, logging).
• LLM-optimized & MCP-ready: Structured 2-line messages with CWE + OWASP + CVSS + concrete fixes so humans and AI auto-fixers stay aligned.
• Standards aligned: OWASP Serverless Top 10, CWE tagging, CVSS scoring in every finding for compliance mapping.
• Tiered presets: recommended, strict for fast policy rollout.
• Framework-aware: Detects Middy middleware, API Gateway response patterns, AWS SDK v3 clients.
• Low false positive rate: Context-aware detection with production heuristics.

Every security rule produces a structured 2-line error message:

src/handlers/api.ts
  18:5   error  🔒 CWE-798 OWASP:SAS-2 CVSS:9.8 | Hardcoded AWS credentials detected | CRITICAL [SOC2,PCI-DSS]
                    Fix: Use credential provider chain or Lambda execution role | https://owasp.org/...

Each message includes:

• 🔒 CWE reference - vulnerability classification
• 📋 OWASP category - Serverless Top 10 mapping
• 📊 CVSS score - severity rating (0.0-10.0)
• 🏢 Compliance tags - affected frameworks (SOC2, PCI-DSS, HIPAA)
• ✅ Fix instruction - exact code to write
• 📚 Documentation link - learn more

📊 OWASP Serverless Top 10 Coverage Matrix

🔐 5 Security Rules

💼 = Set in recommended | ⚠️ = Warns in recommended | 🔧 = Auto-fixable | 💡 = Suggestions

Credential & Secrets Protection (3 rules)

CORS Security (2 rules)

🔍 Rule Details

no-hardcoded-credentials-sdk

Detects hardcoded AWS credentials in AWS SDK v3 client configurations.

❌ Incorrect

// Hardcoded credentials - NEVER do this!
const client = new S3Client({
  credentials: {
    accessKeyId: 'AKIAIOSFODNN7EXAMPLE',
    secretAccessKey: 'wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY',
  },
});

✅ Correct

// Use credential provider chain
import { fromNodeProviderChain } from '@aws-sdk/credential-providers';

const client = new S3Client({
  credentials: fromNodeProviderChain(),
});

// Or let SDK use default chain (recommended for Lambda)
const client = new S3Client({ region: 'us-east-1' });

Detection Patterns:

• Real AWS access key patterns (AKIA*, ASIA*)
• Secret access keys with 20+ characters
• Session tokens with 15+ characters
• Template literal credential construction

no-permissive-cors-response

Detects wildcard CORS (Access-Control-Allow-Origin: '*') in Lambda response headers.

❌ Incorrect

return {
  statusCode: 200,
  headers: { 'Access-Control-Allow-Origin': '*' },
  body: JSON.stringify(data),
};

✅ Correct

return {
  statusCode: 200,
  headers: { 'Access-Control-Allow-Origin': 'https://your-app.com' },
  body: JSON.stringify(data),
};

// Or use dynamic origin from request
return {
  statusCode: 200,
  headers: { 'Access-Control-Allow-Origin': event.headers.origin },
  body: JSON.stringify(data),
};

no-permissive-cors-middy

Detects permissive CORS configuration in Middy http-cors middleware.

❌ Incorrect

// Default is permissive!
middy(handler).use(httpCors());

// Explicit wildcard
middy(handler).use(httpCors({ origin: '*' }));

✅ Correct

middy(handler).use(
  httpCors({
    origins: ['https://your-app.com', 'https://app.your-domain.com'],
  }),
);

no-secrets-in-env

Detects secrets hardcoded in environment variable assignments.

❌ Incorrect

process.env.DB_PASSWORD = 'my-secret-password-12345';

const envConfig = {
  API_KEY: 'sk-1234567890abcdef1234567890abcdef',
};

✅ Correct

// Read from process.env (populated by Lambda)
const password = process.env.DB_PASSWORD;

// Use AWS Secrets Manager
import {
  SecretsManagerClient,
  GetSecretValueCommand,
} from '@aws-sdk/client-secrets-manager';

const secret = await client.send(
  new GetSecretValueCommand({ SecretId: 'my-secret' }),
);

no-env-logging

Detects logging of the entire process.env object, which may expose secrets.

❌ Incorrect

console.log(process.env);
console.log(JSON.stringify(process.env));
logger.info(process.env);

✅ Correct

// Log specific, non-sensitive values
console.log('Region:', process.env.AWS_REGION);
console.log('Environment:', process.env.NODE_ENV);

🚀 Quick Start

ESLint Flat Config (Recommended)

// eslint.config.js
import lambdaSecurity from 'eslint-plugin-lambda-security';

export default [
  lambdaSecurity.configs.recommended,
  // ... other configs
];

Strict Mode

import lambdaSecurity from 'eslint-plugin-lambda-security';

export default [lambdaSecurity.configs.strict];

📋 Available Presets

⚙️ Configuration Options

All rules accept these common options:

{
  rules: {
    'lambda-security/no-hardcoded-credentials-sdk': ['error', {
      allowInTests: true // Default: true - skip test files
    }],
    'lambda-security/no-secrets-in-env': ['error', {
      allowInTests: true,
      additionalPatterns: ['CUSTOM_SECRET_*'] // Additional patterns to detect
    }]
  }
}

🏢 Enterprise Integration Example

// eslint.config.js
import lambdaSecurity from 'eslint-plugin-lambda-security';

export default [
  // Baseline for all Lambda functions
  lambdaSecurity.configs.recommended,

  // Strict mode for payment/auth handlers
  {
    files: ['functions/payments/**', 'functions/auth/**'],
    ...lambdaSecurity.configs.strict,
  },
];

🤖 LLM & AI Integration

This plugin is optimized for ESLint's Model Context Protocol (MCP), enabling AI assistants like Cursor, GitHub Copilot, and Claude to:

• Understand the exact vulnerability type via CWE references
• Apply the correct fix using structured guidance
• Provide educational context to developers

// .cursor/mcp.json
{
  "mcpServers": {
    "eslint": {
      "command": "npx",
      "args": ["@eslint/mcp@latest"]
    }
  }
}

🔗 Related ESLint Plugins

Part of the Interlace ESLint Ecosystem — AI-native security plugins with LLM-optimized error messages:

🔒 Privacy

This plugin runs 100% locally. No data ever leaves your machine.

📄 License

MIT © Ofri Peretz