All skills
semgrep avatar

/code-security

@327da93 official
by semgrepsemgrep/skills316 stars
31

Security guidelines for writing secure code. Use when writing code, reviewing code for vulnerabilities, or asking about secure coding practices like 'check for SQL injection' or 'review security'. IMPORTANT: Always consult this skill when writing or reviewing any code that handles user input, authentication, file operations, database queries, network requests, cryptography, or infrastructure configuration (Terraform, Kubernetes, Docker, GitHub Actions) — even if the user doesn't explicitly mention security. Also use when users ask to 'review my code', 'check this for bugs', or 'is this safe'.

Use this Skill: https://skilld.dev/gh/semgrep/skills/code-security

This session only. Nothing lands on disk.

rulesregex-dos.md

≈949 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Prevent Regular Expression DoS (ReDoS)

Regular Expression Denial of Service (ReDoS) occurs when attackers exploit inefficient regular expression patterns to cause excessive CPU consumption. Certain regex patterns with nested quantifiers or overlapping alternatives can experience "catastrophic backtracking" when matched against malicious input, causing the regex engine to take exponential time to evaluate.

Common vulnerable patterns include:

  • Nested quantifiers: (a+)+, (a*)*, (a|a)+
  • Overlapping alternatives: (a|aa)+
  • Unbounded repetition with overlap: .*.*

Language: JavaScript / TypeScript

Incorrect (vulnerable ReDoS pattern):

const re = new RegExp("([a-z]+)+$", "i");

var emailRegex = /^\w+([-_+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$/;
emailRegex.test(userInput);

Correct (safe regex patterns):

// Use atomic patterns without nested quantifiers
const safeRegex = /^[a-z]+$/i;

// Or use a library with ReDoS protection
import { RE2 } from 're2';
const re = new RE2("([a-z]+)+$");

Incorrect (non-literal RegExp with user input):

function searchHandler(userPattern) {
  const reg = new RegExp("\\w+" + userPattern);
  return reg.exec(data);
}

Correct (hardcoded regex patterns):

function searchHandler(userInput) {
  const reg = new RegExp("\\w+");
  return reg.exec(userInput);
}

Incorrect (incomplete string sanitization):

function escapeQuotes(s) {
  return s.replace("'", "''");  // Only replaces first occurrence
}

Correct (use regex with global flag):

function escapeQuotes(s) {
  return s.replace(/'/g, "''");  // Replaces all occurrences
}

References:


Language: Python

Incorrect (inefficient regex pattern):

import re

redos_pattern = r"^(a+)+$"
data = "aaaaaaaaaaaaaaaaaaaaaaaaaaaaX"

pattern = re.compile(redos_pattern)
pattern.match(data)  # Catastrophic backtracking

Correct (safe regex patterns):

import re

safe_pattern = r"^a+$"
data = "aaaaaaaaaaaaaaaaaaaaaaaaaaaaX"

pattern = re.compile(safe_pattern)
pattern.match(data)  # Fast failure, no backtracking

Mitigation strategies:

# Use regex timeout (Python 3.11+)
import re
re.match(pattern, data, timeout=1.0)

# Or use google-re2 library for linear-time matching
import re2
re2.match(r"^(a+)+$", data)

References:


General Mitigation Strategies

  1. Avoid nested quantifiers: Never use patterns like (a+)+ or (.*)*
  2. Use atomic groups or possessive quantifiers when available
  3. Set timeouts: Use regex timeout mechanisms to limit execution time
  4. Use safe regex libraries: RE2 (Go/Python/JS) guarantees linear-time matching
  5. Validate user input length: Limit input size before regex matching
  6. Test with ReDoS analyzers: Use tools like safe-regex or recheck

References:

Source: SKILL.md on GitHub

2 warnings16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides a comprehensive library of security guidelines and code examples to help AI agents write secure code and perform security reviews. It covers OWASP Top 10 vulnerabilities, infrastructure security (Terraform, Kubernetes, Docker), and general best practices. While the files contain examples of vulnerable code (such as SQL injection and hardcoded secrets), these are used exclusively for educational purposes to demonstrate what to avoid and are part of the 'Incorrect' examples within the security rules.

  • Socket16d

    2 alerts: gptSecurity

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    4/34 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 327da93. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Steadyupdated 7 months ago
  • Security
  • Infrastructure
  • code-review
  • owasp
  • sql-injection
  • xss
  • command-injection
  • authentication
  • terraform
  • kubernetes
  • docker

README badge

README badge for semgrep/skills/code-security

Provides security rules across 15+ languages covering OWASP Top 10 vulnerabilities, infrastructure configuration, and secure coding practices. Includes SQL injection, XSS, command injection, cryptography, and Kubernetes/Terraform security with language-specific priority guidelines and rule files for detailed code examples.

Generated from the current SKILL.md.

Does this skill cover infrastructure security like Terraform and Kubernetes?
Yes. The skill includes 28 rule categories covering Terraform (AWS, Azure, GCP), Kubernetes, Docker, and GitHub Actions alongside language-specific rules for Python, JavaScript, Java, Go, C/C++, Ruby, and PHP.
When should I use this skill — only when the user asks about security?
No. The skill is designed for proactive mode: automatically check for vulnerabilities when writing or reviewing any code that handles user input, authentication, databases, file operations, network requests, cryptography, or infrastructure configuration — even if the user doesn't explicitly mention security.
What vulnerabilities does this skill prioritize?
It prioritizes Critical impact rules first: SQL injection, command injection, XSS, XXE, path traversal, insecure deserialization, code injection, hardcoded secrets, and memory safety. High impact rules include insecure crypto, SSRF, JWT issues, and CSRF.
Does this skill provide code examples for each vulnerability type?
Yes. Each rule category (e.g., `rules/sql-injection.md`) contains detailed vulnerable and secure code examples in the relevant language.

Generated from the current SKILL.md. These answers refresh after source changes.