Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问许可证需确认审计通过

owasp-top-10owasp 前 10 名

Agent Skill

owasp-top-10 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,298

周安装

33

GitHub Stars

12

下载量

261
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:owasp-top-10(owasp 前 10 名)
来源仓库:https://github.com/claude-dev-suite/claude-dev-suite
仓库路径:skills/owasp-top-10
安装命令:
npx skills add https://github.com/claude-dev-suite/claude-dev-suite --skill owasp-top-10
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/claude-dev-suite/claude-dev-suite --skill owasp-top-10

简介

owasp-top-10 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 它提供 OWASP Top 10:2025 的最新安全风险分类,包括访问控制、供应链和注入漏洞等主题。
  • 使用时需结合具体项目技术栈选择合适的防护措施,避免仅依赖通用建议;涉及第三方组件时应加强审核。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

OWASP Top 10:2025

When NOT to Use This Skill

  • OWASP Top 10:2021 - Use owasp skill for 2021 version
  • Detailed secrets management - Use secrets-management skill
  • Detailed supply chain security - Use supply-chain skill for in-depth dependency management
  • License compliance - Use license-compliance skill
Deep Knowledge: Use mcp__documentation__fetch_docs with technology: owasp for comprehensive documentation.

Quick Reference

RankCategoryPrevention
A01Broken Access ControlAuthorization checks, deny by default
A02Security MisconfigurationHardening, security headers, no defaults
A03Supply Chain FailuresDependency audits, lockfiles, SBOMs
A04Cryptographic FailuresStrong algorithms, proper key management
A05InjectionParameterized queries, input validation
A06Insecure DesignThreat modeling, secure patterns
A07Authentication FailuresMFA, rate limiting, secure sessions
A08Integrity FailuresSigned updates, safe deserialization
A09Logging FailuresAudit logs, alerting, monitoring
A10Exception HandlingGraceful errors, no info leakage

A01: Broken Access Control

// Always verify ownership
if (resource.userId !== currentUser.id) {
  throw new ForbiddenException();
}

// Deny by default
const allowed = permissions.includes(requiredPermission);
if (!allowed) throw new ForbiddenException();

// Rate limit sensitive endpoints
app.use('/api/admin/*', adminRateLimiter);

A02: Security Misconfiguration

// Security headers
import helmet from 'helmet';
app.use(helmet());

// Strict CORS
app.use(cors({
  origin: ['https://myapp.com'],
  credentials: true
}));

// Hide errors in production
if (process.env.NODE_ENV === 'production') {
  app.use((err, req, res, next) => {
    res.status(500).json({ error: 'Internal error' });
  });
}

A03: Supply Chain Failures (NEW in 2025)

# Audit dependencies
npm audit
pip-audit
mvn dependency-check:check

# Use lockfiles
npm ci  # Instead of npm install

# Verify package integrity
npm install --ignore-scripts
npm config set ignore-scripts true

A04: Cryptographic Failures

// Strong password hashing
import { hash, verify } from 'argon2';
const hashed = await hash(password, { type: argon2id });

// Secure random
import { randomBytes, randomUUID } from 'crypto';
const token = randomBytes(32).toString('hex');

// AES-256-GCM for encryption (not CBC)

A05: Injection

// SQL - use parameterized queries
const user = await prisma.user.findUnique({ where: { id } });
await db.query('SELECT * FROM users WHERE id = $1', [id]);

// Command - use execFile, not exec
import { execFile } from 'child_process';
execFile('ls', ['-la', safeArg]);

// XSS - sanitize HTML
import DOMPurify from 'dompurify';
element.innerHTML = DOMPurify.sanitize(userInput);

A06: Insecure Design

Key practices:

  • Threat modeling during design phase
  • Secure design patterns (fail-safe, defense in depth)
  • Security requirements in user stories
  • Abuse case testing

A07: Authentication Failures

// Rate limiting
import rateLimit from 'express-rate-limit';
const loginLimiter = rateLimit({
  windowMs: 15 * 60 * 1000,
  max: 5
});

// Secure cookies
res.cookie('session', token, {
  httpOnly: true,
  secure: true,
  sameSite: 'strict'
});

// Strong passwords (12+ chars, mixed)

A08: Integrity Failures

// Verify signatures on updates
// Use subresource integrity (SRI)
<script src="lib.js"
  integrity="sha384-..."
  crossorigin="anonymous">
</script>

// Safe deserialization
// Avoid: JSON.parse(untrusted)
// Use: zod/yup validation

A09: Logging & Alerting Failures

// Log security events
logger.warn({
  event: 'auth_failure',
  userId: attemptedId,
  ip: req.ip,
  timestamp: new Date().toISOString()
});

// Events to log:
// - Login success/failure
// - Password changes
// - Permission denied
// - Rate limit exceeded

A10: Exception Handling (NEW in 2025)

// Graceful error handling
try {
  await riskyOperation();
} catch (error) {
  logger.error({ error, context });
  // Generic response to user
  throw new InternalServerException('Operation failed');
}

// Never expose stack traces
// Never expose internal paths
// Never expose SQL/DB errors

Security Scanning Commands

# Dependencies
npm audit --json
snyk test

# Secrets
gitleaks detect
trufflehog git file://.

# SAST
semgrep --config=p/security-audit .

# Docker
trivy image myimage:latest

Checklist

RiskPrevention
SQL InjectionParameterized queries, ORMs
XSSEscape output, CSP headers
CSRFCSRF tokens, SameSite cookies
Auth issuesMFA, rate limiting, secure sessions
SecretsEnvironment variables, vaults
Supply chainAudit, lockfiles, SBOMs

Anti-Patterns

Anti-PatternWhy It's BadCorrect Approach
Checking permissions in frontend onlyClient-side bypass (A01)Always verify on backend
Using weak crypto (MD5, DES)Easily broken (A04)Use AES-256-GCM, argon2, SHA-256+
npm install in CI/CDNon-deterministic builds (A03)Use npm ci with lockfiles
Catching all exceptions silentlyHides security issues (A10)Log errors, fail gracefully
Trusting user input in queriesInjection attacks (A05)Always use parameterized queries
No session timeoutSession hijacking (A07)Implement idle + absolute timeout

Quick Troubleshooting

IssueLikely CauseSolution
npm audit shows vulnerabilitiesOutdated dependencies (A03)Run npm audit fix or update manually
Login always fails after 5 attemptsRate limiter too strict (A07)Review rate limit settings
Secrets leaked in git historyCommitted.env file (A02)Use BFG to clean history, rotate secrets
Database queries slow/failingSQL injection attack (A05)Review logs, switch to parameterized queries
Users accessing others' dataMissing authorization (A01)Add ownership checks in all endpoints
Stack traces in productionException handling disabled (A10)Enable production error handling

Related Skills

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.54%
按下载量换算93

Claude

32.37%
按下载量换算84

Cursor

17.88%
按下载量换算47

Gemini CLI

10.63%
按下载量换算28

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills