perl-security — taint mode configuration perl-security, everything-claude-code, affaan-m, official, taint mode configuration, ai agent skill, mcp server, agent automation, DBI parameterized queries, XSS prevention techniques, SQL injection prevention, perlcritic security policies

Verified
v1.0.0
GitHub

About this Skill

Ideal for Security Analysis Agents requiring comprehensive Perl security auditing and vulnerability assessment capabilities. perl-security is a set of comprehensive guidelines for securing Perl applications, covering taint mode, input validation, and secure coding practices.

Features

Enforces taint mode for secure input handling
Validates user input to prevent injection attacks
Supports DBI parameterized queries for secure database interactions
Prevents cross-site scripting (XSS) and SQL injection (SQLi) attacks
Implements perlcritic security policies for code review
Secures process execution and file operations with user-supplied paths

# Core Topics

affaan-m affaan-m
[78.3k]
[9920]
Updated: 3/16/2026

Quality Score

Top 5%
95
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
> npx killer-skills add affaan-m/everything-claude-code/perl-security
Supports 18+ Platforms
Cursor
Windsurf
VS Code
Trae
Claude
OpenClaw
+12 more

Agent Capability Analysis

The perl-security MCP Server by affaan-m is an open-source official integration for Claude and other AI agents, enabling seamless task automation and capability expansion. Optimized for taint mode configuration, DBI parameterized queries, XSS prevention techniques.

Ideal Agent Persona

Ideal for Security Analysis Agents requiring comprehensive Perl security auditing and vulnerability assessment capabilities.

Core Value

Empowers agents to enforce taint mode, validate user input, and execute safe DBI parameterized queries, ensuring robust protection against XSS, SQLi, and CSRF attacks in Perl web applications using frameworks like CGI, Mojolicious, Dancer2, and Catalyst.

Capabilities Granted for perl-security MCP Server

Validating user input in Perl applications to prevent injection attacks
Auditing Perl code for security vulnerabilities using perlcritic policies
Securing DBI database queries with parameterized inputs to prevent SQL injection

! Prerequisites & Limits

  • Requires Perl programming language support
  • Limited to Perl-specific security vulnerabilities and best practices
Project
SKILL.md
13.2 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8
SKILL.md
Readonly

Perl Security Patterns

Comprehensive security guidelines for Perl applications covering input validation, injection prevention, and secure coding practices.

When to Activate

  • Handling user input in Perl applications
  • Building Perl web applications (CGI, Mojolicious, Dancer2, Catalyst)
  • Reviewing Perl code for security vulnerabilities
  • Performing file operations with user-supplied paths
  • Executing system commands from Perl
  • Writing DBI database queries

How It Works

Start with taint-aware input boundaries, then move outward: validate and untaint inputs, keep filesystem and process execution constrained, and use parameterized DBI queries everywhere. The examples below show the safe defaults this skill expects you to apply before shipping Perl code that touches user input, the shell, or the network.

Taint Mode

Perl's taint mode (-T) tracks data from external sources and prevents it from being used in unsafe operations without explicit validation.

Enabling Taint Mode

perl
1#!/usr/bin/perl -T 2use v5.36; 3 4# Tainted: anything from outside the program 5my $input = $ARGV[0]; # Tainted 6my $env_path = $ENV{PATH}; # Tainted 7my $form = <STDIN>; # Tainted 8my $query = $ENV{QUERY_STRING}; # Tainted 9 10# Sanitize PATH early (required in taint mode) 11$ENV{PATH} = '/usr/local/bin:/usr/bin:/bin'; 12delete @ENV{qw(IFS CDPATH ENV BASH_ENV)};

Untainting Pattern

perl
1use v5.36; 2 3# Good: Validate and untaint with a specific regex 4sub untaint_username($input) { 5 if ($input =~ /^([a-zA-Z0-9_]{3,30})$/) { 6 return $1; # $1 is untainted 7 } 8 die "Invalid username: must be 3-30 alphanumeric characters\n"; 9} 10 11# Good: Validate and untaint a file path 12sub untaint_filename($input) { 13 if ($input =~ m{^([a-zA-Z0-9._-]+)$}) { 14 return $1; 15 } 16 die "Invalid filename: contains unsafe characters\n"; 17} 18 19# Bad: Overly permissive untainting (defeats the purpose) 20sub bad_untaint($input) { 21 $input =~ /^(.*)$/s; 22 return $1; # Accepts ANYTHING — pointless 23}

Input Validation

Allowlist Over Blocklist

perl
1use v5.36; 2 3# Good: Allowlist — define exactly what's permitted 4sub validate_sort_field($field) { 5 my %allowed = map { $_ => 1 } qw(name email created_at updated_at); 6 die "Invalid sort field: $field\n" unless $allowed{$field}; 7 return $field; 8} 9 10# Good: Validate with specific patterns 11sub validate_email($email) { 12 if ($email =~ /^([a-zA-Z0-9._%+-]+\@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,})$/) { 13 return $1; 14 } 15 die "Invalid email address\n"; 16} 17 18sub validate_integer($input) { 19 if ($input =~ /^(-?\d{1,10})$/) { 20 return $1 + 0; # Coerce to number 21 } 22 die "Invalid integer\n"; 23} 24 25# Bad: Blocklist — always incomplete 26sub bad_validate($input) { 27 die "Invalid" if $input =~ /[<>"';&|]/; # Misses encoded attacks 28 return $input; 29}

Length Constraints

perl
1use v5.36; 2 3sub validate_comment($text) { 4 die "Comment is required\n" unless length($text) > 0; 5 die "Comment exceeds 10000 chars\n" if length($text) > 10_000; 6 return $text; 7}

Safe Regular Expressions

ReDoS Prevention

Catastrophic backtracking occurs with nested quantifiers on overlapping patterns.

perl
1use v5.36; 2 3# Bad: Vulnerable to ReDoS (exponential backtracking) 4my $bad_re = qr/^(a+)+$/; # Nested quantifiers 5my $bad_re2 = qr/^([a-zA-Z]+)*$/; # Nested quantifiers on class 6my $bad_re3 = qr/^(.*?,){10,}$/; # Repeated greedy/lazy combo 7 8# Good: Rewrite without nesting 9my $good_re = qr/^a+$/; # Single quantifier 10my $good_re2 = qr/^[a-zA-Z]+$/; # Single quantifier on class 11 12# Good: Use possessive quantifiers or atomic groups to prevent backtracking 13my $safe_re = qr/^[a-zA-Z]++$/; # Possessive (5.10+) 14my $safe_re2 = qr/^(?>a+)$/; # Atomic group 15 16# Good: Enforce timeout on untrusted patterns 17use POSIX qw(alarm); 18sub safe_match($string, $pattern, $timeout = 2) { 19 my $matched; 20 eval { 21 local $SIG{ALRM} = sub { die "Regex timeout\n" }; 22 alarm($timeout); 23 $matched = $string =~ $pattern; 24 alarm(0); 25 }; 26 alarm(0); 27 die $@ if $@; 28 return $matched; 29}

Safe File Operations

Three-Argument Open

perl
1use v5.36; 2 3# Good: Three-arg open, lexical filehandle, check return 4sub read_file($path) { 5 open my $fh, '<:encoding(UTF-8)', $path 6 or die "Cannot open '$path': $!\n"; 7 local $/; 8 my $content = <$fh>; 9 close $fh; 10 return $content; 11} 12 13# Bad: Two-arg open with user data (command injection) 14sub bad_read($path) { 15 open my $fh, $path; # If $path = "|rm -rf /", runs command! 16 open my $fh, "< $path"; # Shell metacharacter injection 17}

TOCTOU Prevention and Path Traversal

perl
1use v5.36; 2use Fcntl qw(:DEFAULT :flock); 3use File::Spec; 4use Cwd qw(realpath); 5 6# Atomic file creation 7sub create_file_safe($path) { 8 sysopen(my $fh, $path, O_WRONLY | O_CREAT | O_EXCL, 0600) 9 or die "Cannot create '$path': $!\n"; 10 return $fh; 11} 12 13# Validate path stays within allowed directory 14sub safe_path($base_dir, $user_path) { 15 my $real = realpath(File::Spec->catfile($base_dir, $user_path)) 16 // die "Path does not exist\n"; 17 my $base_real = realpath($base_dir) 18 // die "Base dir does not exist\n"; 19 die "Path traversal blocked\n" unless $real =~ /^\Q$base_real\E(?:\/|\z)/; 20 return $real; 21}

Use File::Temp for temporary files (tempfile(UNLINK => 1)) and flock(LOCK_EX) to prevent race conditions.

Safe Process Execution

List-Form system and exec

perl
1use v5.36; 2 3# Good: List form — no shell interpolation 4sub run_command(@cmd) { 5 system(@cmd) == 0 6 or die "Command failed: @cmd\n"; 7} 8 9run_command('grep', '-r', $user_pattern, '/var/log/app/'); 10 11# Good: Capture output safely with IPC::Run3 12use IPC::Run3; 13sub capture_output(@cmd) { 14 my ($stdout, $stderr); 15 run3(\@cmd, \undef, \$stdout, \$stderr); 16 if ($?) { 17 die "Command failed (exit $?): $stderr\n"; 18 } 19 return $stdout; 20} 21 22# Bad: String form — shell injection! 23sub bad_search($pattern) { 24 system("grep -r '$pattern' /var/log/app/"); # If $pattern = "'; rm -rf / #" 25} 26 27# Bad: Backticks with interpolation 28my $output = `ls $user_dir`; # Shell injection risk

Also use Capture::Tiny for capturing stdout/stderr from external commands safely.

SQL Injection Prevention

DBI Placeholders

perl
1use v5.36; 2use DBI; 3 4my $dbh = DBI->connect($dsn, $user, $pass, { 5 RaiseError => 1, 6 PrintError => 0, 7 AutoCommit => 1, 8}); 9 10# Good: Parameterized queries — always use placeholders 11sub find_user($dbh, $email) { 12 my $sth = $dbh->prepare('SELECT * FROM users WHERE email = ?'); 13 $sth->execute($email); 14 return $sth->fetchrow_hashref; 15} 16 17sub search_users($dbh, $name, $status) { 18 my $sth = $dbh->prepare( 19 'SELECT * FROM users WHERE name LIKE ? AND status = ? ORDER BY name' 20 ); 21 $sth->execute("%$name%", $status); 22 return $sth->fetchall_arrayref({}); 23} 24 25# Bad: String interpolation in SQL (SQLi vulnerability!) 26sub bad_find($dbh, $email) { 27 my $sth = $dbh->prepare("SELECT * FROM users WHERE email = '$email'"); 28 # If $email = "' OR 1=1 --", returns all users 29 $sth->execute; 30 return $sth->fetchrow_hashref; 31}

Dynamic Column Allowlists

perl
1use v5.36; 2 3# Good: Validate column names against an allowlist 4sub order_by($dbh, $column, $direction) { 5 my %allowed_cols = map { $_ => 1 } qw(name email created_at); 6 my %allowed_dirs = map { $_ => 1 } qw(ASC DESC); 7 8 die "Invalid column: $column\n" unless $allowed_cols{$column}; 9 die "Invalid direction: $direction\n" unless $allowed_dirs{uc $direction}; 10 11 my $sth = $dbh->prepare("SELECT * FROM users ORDER BY $column $direction"); 12 $sth->execute; 13 return $sth->fetchall_arrayref({}); 14} 15 16# Bad: Directly interpolating user-chosen column 17sub bad_order($dbh, $column) { 18 $dbh->prepare("SELECT * FROM users ORDER BY $column"); # SQLi! 19}

DBIx::Class (ORM Safety)

perl
1use v5.36; 2 3# DBIx::Class generates safe parameterized queries 4my @users = $schema->resultset('User')->search({ 5 status => 'active', 6 email => { -like => '%@example.com' }, 7}, { 8 order_by => { -asc => 'name' }, 9 rows => 50, 10});

Web Security

XSS Prevention

perl
1use v5.36; 2use HTML::Entities qw(encode_entities); 3use URI::Escape qw(uri_escape_utf8); 4 5# Good: Encode output for HTML context 6sub safe_html($user_input) { 7 return encode_entities($user_input); 8} 9 10# Good: Encode for URL context 11sub safe_url_param($value) { 12 return uri_escape_utf8($value); 13} 14 15# Good: Encode for JSON context 16use JSON::MaybeXS qw(encode_json); 17sub safe_json($data) { 18 return encode_json($data); # Handles escaping 19} 20 21# Template auto-escaping (Mojolicious) 22# <%= $user_input %> — auto-escaped (safe) 23# <%== $raw_html %> — raw output (dangerous, use only for trusted content) 24 25# Template auto-escaping (Template Toolkit) 26# [% user_input | html %] — explicit HTML encoding 27 28# Bad: Raw output in HTML 29sub bad_html($input) { 30 print "<div>$input</div>"; # XSS if $input contains <script> 31}

CSRF Protection

perl
1use v5.36; 2use Crypt::URandom qw(urandom); 3use MIME::Base64 qw(encode_base64url); 4 5sub generate_csrf_token() { 6 return encode_base64url(urandom(32)); 7}

Use constant-time comparison when verifying tokens. Most web frameworks (Mojolicious, Dancer2, Catalyst) provide built-in CSRF protection — prefer those over hand-rolled solutions.

Session and Header Security

perl
1use v5.36; 2 3# Mojolicious session + headers 4$app->secrets(['long-random-secret-rotated-regularly']); 5$app->sessions->secure(1); # HTTPS only 6$app->sessions->samesite('Lax'); 7 8$app->hook(after_dispatch => sub ($c) { 9 $c->res->headers->header('X-Content-Type-Options' => 'nosniff'); 10 $c->res->headers->header('X-Frame-Options' => 'DENY'); 11 $c->res->headers->header('Content-Security-Policy' => "default-src 'self'"); 12 $c->res->headers->header('Strict-Transport-Security' => 'max-age=31536000; includeSubDomains'); 13});

Output Encoding

Always encode output for its context: HTML::Entities::encode_entities() for HTML, URI::Escape::uri_escape_utf8() for URLs, JSON::MaybeXS::encode_json() for JSON.

CPAN Module Security

  • Pin versions in cpanfile: requires 'DBI', '== 1.643';
  • Prefer maintained modules: Check MetaCPAN for recent releases
  • Minimize dependencies: Each dependency is an attack surface

Security Tooling

perlcritic Security Policies

ini
1# .perlcriticrc — security-focused configuration 2severity = 3 3theme = security + core 4 5# Require three-arg open 6[InputOutput::RequireThreeArgOpen] 7severity = 5 8 9# Require checked system calls 10[InputOutput::RequireCheckedSyscalls] 11functions = :builtins 12severity = 4 13 14# Prohibit string eval 15[BuiltinFunctions::ProhibitStringyEval] 16severity = 5 17 18# Prohibit backtick operators 19[InputOutput::ProhibitBacktickOperators] 20severity = 4 21 22# Require taint checking in CGI 23[Modules::RequireTaintChecking] 24severity = 5 25 26# Prohibit two-arg open 27[InputOutput::ProhibitTwoArgOpen] 28severity = 5 29 30# Prohibit bare-word filehandles 31[InputOutput::ProhibitBarewordFileHandles] 32severity = 5

Running perlcritic

bash
1# Check a file 2perlcritic --severity 3 --theme security lib/MyApp/Handler.pm 3 4# Check entire project 5perlcritic --severity 3 --theme security lib/ 6 7# CI integration 8perlcritic --severity 4 --theme security --quiet lib/ || exit 1

Quick Security Checklist

CheckWhat to Verify
Taint mode-T flag on CGI/web scripts
Input validationAllowlist patterns, length limits
File operationsThree-arg open, path traversal checks
Process executionList-form system, no shell interpolation
SQL queriesDBI placeholders, never interpolate
HTML outputencode_entities(), template auto-escape
CSRF tokensGenerated, verified on state-changing requests
Session configSecure, HttpOnly, SameSite cookies
HTTP headersCSP, X-Frame-Options, HSTS
DependenciesPinned versions, audited modules
Regex safetyNo nested quantifiers, anchored patterns
Error messagesNo stack traces or paths leaked to users

Anti-Patterns

perl
1# 1. Two-arg open with user data (command injection) 2open my $fh, $user_input; # CRITICAL vulnerability 3 4# 2. String-form system (shell injection) 5system("convert $user_file output.png"); # CRITICAL vulnerability 6 7# 3. SQL string interpolation 8$dbh->do("DELETE FROM users WHERE id = $id"); # SQLi 9 10# 4. eval with user input (code injection) 11eval $user_code; # Remote code execution 12 13# 5. Trusting $ENV without sanitizing 14my $path = $ENV{UPLOAD_DIR}; # Could be manipulated 15system("ls $path"); # Double vulnerability 16 17# 6. Disabling taint without validation 18($input) = $input =~ /(.*)/s; # Lazy untaint — defeats purpose 19 20# 7. Raw user data in HTML 21print "<div>Welcome, $username!</div>"; # XSS 22 23# 8. Unvalidated redirects 24print $cgi->redirect($user_url); # Open redirect

Remember: Perl's flexibility is powerful but requires discipline. Use taint mode for web-facing code, validate all input with allowlists, use DBI placeholders for every query, and encode all output for its context. Defense in depth — never rely on a single layer.

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is perl-security?

Ideal for Security Analysis Agents requiring comprehensive Perl security auditing and vulnerability assessment capabilities. perl-security is a set of comprehensive guidelines for securing Perl applications, covering taint mode, input validation, and secure coding practices.

How do I install perl-security?

Run the command: npx killer-skills add affaan-m/everything-claude-code/perl-security. It works with Cursor, Windsurf, VS Code, Claude Code, and 15+ other IDEs.

What are the use cases for perl-security?

Key use cases include: Validating user input in Perl applications to prevent injection attacks, Auditing Perl code for security vulnerabilities using perlcritic policies, Securing DBI database queries with parameterized inputs to prevent SQL injection.

Which IDEs are compatible with perl-security?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for perl-security?

Requires Perl programming language support. Limited to Perl-specific security vulnerabilities and best practices.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add affaan-m/everything-claude-code/perl-security. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use perl-security immediately in the current project.

Related Skills

Looking for an alternative to perl-security or building a official AI Agent? Explore these related open-source MCP Servers.

View All

flags

Logo of facebook
facebook

flags is a feature flag management tool that enables developers to check flag states, compare channels, and debug issues across different release channels.

244.0k
0
Design

extract-errors

Logo of facebook
facebook

The extract-errors skill is a React tool that extracts error codes and updates them for frontend development.

244.0k
0
Design

fix

Logo of facebook
facebook

fix is a skill that resolves lint errors and formatting issues in JavaScript code using yarn prettier and yarn linc.

244.0k
0
Design

flow

Logo of facebook
facebook

Flow is a type checking system for JavaScript, enabling developers to catch type errors in their React code.

244.0k
0
Design