trailofbits/constant-time-testing

Testes de tempo constante detectam canais laterais de temporização em código criptográfico. Use ao auditar implementações criptográficas em busca de vulnerabilidades de temporização.

O que é constant-time-testing?

Esta skill, baseada na ferramenta `dudect` (de 'do not use differential execution time'), permite testar se o tempo de execução de uma função criptográfica é constante e independente de segredos. É essencial para identificar canais laterais de temporização que podem vazar chaves ou dados confidenciais em implementações reais. A skill analisa o código-fonte ou binários, medindo variações de tempo para diferentes entradas e detectando dependências não constantes em operações como comparações, desvios condicionais ou acesso a memória baseado em segredos. Suporta diversas plataformas e linguagens (C, Rust, Go, etc.) e integra-se a fluxos de CI/CD, gerando relatórios claros sobre falhas ou aprovações. Com esta skill, desenvolvedores e auditores podem verificar rigorosamente se algoritmos como AES, RSA ou ECDSA estão livres de vazamentos de temporização, prevenindo ataques práticos como os de Bernstein ou de cache.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/trailofbits/skills/tree/main/skills/constant-time-testing

Installed? Explore more Programação e Desenvolvimento skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

O que constant-time-testing faz?

Testes de tempo constante detectam canais laterais de temporização em código criptográfico. Use ao auditar implementações criptográficas em busca de vulnerabilidades de temporização.

Descrição

Esta skill emprega a ferramenta dudect para realizar testes estatísticos de temporização. Ela executa uma função alvo com entradas aleatórias e mede o tempo de execução, aplicando um teste de hipótese para determinar se a variância observada é estatisticamente significativa. Se for, isso indica que o código não é de tempo constante, potencialmente vazando informações secretas.

Como usar

Adicione esta skill ao seu agente (por exemplo, Claude Code, Cursor) para que ele reconheça e execute testes de tempo constante automaticamente durante auditorias de código criptográfico. O agente irá:

  1. Identificar funções criptográficas no código-fonte (por exemplo, implementações de AES, RSA, ECDSA).
  2. Instrumentar o código com dudect para medir tempos de execução.
  3. Analisar os resultados e reportar se há desvios temporais significativos.

Plataformas suportadas

  • Linguagens: C, Rust, Go, Python (com wrappers)
  • Sistemas: Linux, macOS, Windows (via WSL ou Docker)
  • CI/CD: Integração com GitHub Actions, GitLab CI, Jenkins

Exemplo de saída

[INFO] Testing function: aes_encrypt_block
[INFO] Measuring execution time for 1000 iterations...
[WARNING] Timing variation detected: p-value = 0.003
[FAIL] Function is NOT constant-time.

Leitura adicional


Documentação gerada pela skill trailofbits/constant-time-testing.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

trailofbits/address-sanitizer

AddressSanitizer detects memory errors during fuzzing. Use when fuzzing C/C++ code to find buffer overflows and use-after-free bugs.

trailofbits/aflpp

AFL++ is a fork of AFL with better fuzzing performance and advanced features. Use for multi-core fuzzing of C/C++ projects.

trailofbits/agentic-actions-auditor

Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI/CD pipeline security for prompt injection risks, or evaluating agentic action configurations.

trailofbits/algorand-vulnerability-scanner

Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL/PyTeal).

trailofbits/ask-questions-if-underspecified

Clarify requirements before implementing. Use when serious doubts arise.

trailofbits/atheris

Atheris is a coverage-guided Python fuzzer based on libFuzzer. Use for fuzzing pure Python code and Python C extensions.

trailofbits/audit-augmentation

Augments Trailmark code graphs with external audit findings from SARIF static analysis results and weAudit annotation files. Maps findings to graph nodes by file and line overlap, creates severity-based subgraphs, and enables cross-referencing findings with pre-analysis data (blast radius, taint, etc.). Use when projecting SARIF results onto a code graph, overlaying weAudit annotations, cross-referencing Semgrep or CodeQL findings with call graph data, or visualizing audit findings in the context of code structure.

trailofbits/audit-context-building

Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.

trailofbits/audit-prep-assistant

Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments).

trailofbits/burpsuite-project-parser

Searches and explores Burp Suite project files (.burp) from the command line. Use when searching response headers or bodies with regex patterns, extracting security audit findings, dumping proxy history or site map data, or analyzing HTTP traffic captured in a Burp project.

trailofbits/cairo-vulnerability-scanner

Scans Cairo/StarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects.

trailofbits/cargo-fuzz

cargo-fuzz is the de facto fuzzing tool for Rust projects using Cargo. Use for fuzzing Rust code with libFuzzer backend.

trailofbits/chrome-mcp-troubleshooting

Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.

trailofbits/claude-in-chrome-troubleshooting

Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.

trailofbits/code-improver

Runs an autonomous review-and-fix improvement loop over any code target — a skill, plugin, module, or directory — using a reviewer the user names: any installed skill or agent. Keeps a cross-round findings ledger, escalates when fixes stop converging, and guards scope mechanically. Use when asked to 'improve this code until review passes', 'run an improvement loop with <reviewer>', or to iterate review-and-fix with a specific reviewer. For skills prefer the skill-improver entry; for a branch prefer pr-improver.

trailofbits/code-maturity-assessor

Systematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing. Produces professional scorecard with evidence-based ratings and actionable recommendations.

trailofbits/codeql

Scans a codebase for security vulnerabilities using CodeQL's interprocedural data flow and taint tracking analysis. Triggers on "run codeql", "codeql scan", "codeql analysis", "build codeql database", or "find vulnerabilities with codeql". Supports "run all" (security-and-quality + security-experimental suites) and "important only" (high-precision security findings) scan modes. Also handles creating data extension models and processing CodeQL SARIF output.

trailofbits/constant-time-analysis

Detects timing side-channel vulnerabilities in cryptographic code. Use when implementing or reviewing crypto code, encountering division on secrets, secret-dependent branches, or constant-time programming questions in C, C++, Go, Rust, Swift, Java, Kotlin, C#, PHP, JavaScript, TypeScript, Python, or Ruby.

trailofbits/cosmos-vulnerability-scanner

Scans Cosmos SDK blockchain modules and CosmWasm contracts for consensus-critical vulnerabilities — chain halts, fund loss, state divergence. 25 core + 16 IBC + 10 EVM + 3 CosmWasm patterns. Use when auditing custom x/ modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.

trailofbits/coverage-analysis

Coverage analysis measures code exercised during fuzzing. Use when assessing harness effectiveness or identifying fuzzing blockers.

Habilidades Relacionadas