eslint-plugin-lambda-security

v1.1.1

Published

2 days ago

Security-focused ESLint plugin for AWS Lambda and Middy applications. Detects insecure API Gateway responses, missing security headers, CORS misconfigurations, input validation issues, and more.

Downloads

809

Description

This plugin secures your AWS Lambda functions by enforcing best practices related to IAM permissions, timeout configurations, and environment variable management. It proactively detects vulnerabilities such as over-permissive policies and insecure logging practices, helping you adhere to the Principle of Least Privilege. Implementing these checks ensures that your serverless architecture remains resilient and compliant with strict security standards.

Philosophy

Interlace fosters strength through integration. Instead of stacking isolated rules, we interlace security directly into your workflow to create a resilient fabric of code. We believe tools should guide rather than gatekeep, providing educational feedback that strengthens the developer with every interaction.

Getting Started

To check out the guide, visit eslint.interlace.tools. 📚
要查看中文指南, 请访问 eslint.interlace.tools. 📚
가이드 문서는 eslint.interlace.tools에서 확인하실 수 있습니다. 📚
ガイドは eslint.interlace.toolsでご確認ください。 📚
Para ver la guía, visita eslint.interlace.tools. 📚
للاطلاع على الدليل، قم بزيارة eslint.interlace.tools. 📚

npm install eslint-plugin-lambda-security --save-dev

💡 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

⚙️ Configuration Presets

📚 Supported Libraries

⚙️ 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,
  },
];

Rules

Legend

| Icon | Description | | :--: | :----------------------------------------------------------------- | | 💼 | Recommended: Included in the recommended preset. | | ⚠️ | Warns: Set towarn in recommended preset. | | 🔧 | Auto-fixable: Automatically fixable by the --fix CLI option. | | 💡 | Suggestions: Providing code suggestions in IDE. | | 🚫 | Deprecated: This rule is deprecated. |

| Rule | CWE | OWASP | CVSS | Description | 💼 | ⚠️ | 🔧 | 💡 | 🚫 | | :--------------------------------------------------------------------------------------------------------------------------- | :-----: | :----: | :--: | :------------------------------------------------------------------ | :-: | :-: | :-: | :-: | :-: | | no-hardcoded-credentials-sdk | CWE-798 | SAS-02 | 9.8 | no-hardcoded-credentials-sdk | 💼 | | | | | | no-permissive-cors-response | CWE-942 | SAS-04 | 9.1 | no-permissive-cors-response | 💼 | | 🔧 | | | | no-permissive-cors-middy | CWE-942 | SAS-04 | 9.1 | no-permissive-cors-middy | 💼 | | | | | | no-secrets-in-env | CWE-522 | SAS-03 | 9.8 | no-secrets-in-env | 💼 | | | | | | no-env-logging | CWE-532 | SAS-03 | 7.5 | no-env-logging | 💼 | ⚠️ | | | | | no-error-swallowing | CWE-391 | SAS-06 | 7.5 | no-error-swallowing | 💼 | ⚠️ | | | | | require-timeout-handling | CWE-703 | SAS-07 | 7.5 | require-timeout-handling | 💼 | ⚠️ | | | | | no-unbounded-batch-processing | CWE-400 | SAS-07 | 7.5 | no-unbounded-batch-processing | 💼 | ⚠️ | | | | | no-unvalidated-event-body | CWE-20 | SAS-01 | 7.5 | no-unvalidated-event-body | 💼 | ⚠️ | | | | | no-missing-authorization-check | CWE-862 | SAS-05 | 7.5 | no-missing-authorization-check | 💼 | ⚠️ | | | | | no-exposed-error-details | CWE-209 | SAS-09 | 7.5 | no-exposed-error-details | 💼 | ⚠️ | | | | | no-user-controlled-requests | CWE-918 | SAS-08 | 9.8 | no-user-controlled-requests | 💼 | | | | | | no-overly-permissive-iam-policy | CWE-732 | SAS-05 | 9.8 | no-overly-permissive-iam-policy | 💼 | | | | |

AI-Optimized Messages

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

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/...

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

By providing this structured context (CWE, OWASP, Fix), we enable AI tools to reason about the security flaw rather than hallucinating. This allows Copilot/Cursor to suggest the exact correct fix immediately.