'vulnerability' 검색 결과

Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

저장소에서 외부 요청이나 사용자 입력으로 악용할 수 있는 취약점을 찾습니다. 입력 경로와 재현 절차, 영향을 확인해 버그 바운티 보고서 작성을 지원합니다.

• 외부 요청으로 도달 가능한 취약점 조사
• 정적 분석 결과 검토
• 최소 재현 절차와 영향 정리

Coordinate Paperclip vulnerability response from confidential report review and private fixes to local testing, CVE identifier requests, advisory publication, and immediate security releases, with human assistance for reporter communication.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a confidential vulnerability report
• Developing and testing a fix in a private fork
• Coordinating advisory publication and a security release

Check third-party packages for known security vulnerabilities, review dependency versions and lock files, and plan updates or replacements. The skill also guides automated scanning in CI, the pipeline that runs project checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking dependencies before a production deployment
• Investigating a reported package vulnerability
• Adding automated dependency scanning to CI

Organize authorized bug bounty investigations from scope review through reconnaissance, asset discovery, vulnerability testing, and reporting. Use vulnerability-specific guides to prioritize checks and prepare reproducible findings with evidence, impact, and remediation advice.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a bug bounty program's scope and testing rules
• Gather public information and discover target assets
• Plan API authorization and business logic checks

Set up automated security checks that inspect source code without running the application. Configure Semgrep, SonarQube, or CodeQL, add project-specific rules, reduce false alarms, and define criteria for blocking problematic changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding automated security scans to CI/CD
• Creating security rules for project-specific code patterns
• Reducing false alarms and scan time

Configure GitHub Dependabot to keep dependencies, the packages a project relies on, updated. Organize update pull requests into groups, set schedules and exclusion rules, and configure security updates across projects with multiple packages or package systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create or revise dependabot.yml
• Group dependency updates into fewer pull requests
• Configure updates across a monorepo

Check AI agent skills before installation by inspecting code, instructions, dependencies, and file access without running the code. Receive a PASS, WARN, or FAIL verdict with findings ranked by severity and suggested fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking an unfamiliar skill before installation
• Finding suspicious instructions in SKILL.md
• Reviewing scripts for credential theft or data leaks

Audit dependency files across eight language ecosystems for built-in vulnerability patterns, license conflicts, and indirect dependency risks. Generate a prioritized upgrade plan with testing and rollback notes, and pair results with live audit tools for current vulnerability coverage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing third-party packages before a release
• Checking dependencies against built-in CVE patterns
• Reviewing license conflicts across dependency chains

Assess web applications, APIs, and infrastructure for security weaknesses through authorized testing. The skill guides code review, dependency and secret scanning, targeted vulnerability checks, and report creation with evidence, severity ratings, and remediation priorities.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check a web application against the OWASP Top 10
• Test API authentication and access controls
• Scan dependencies and Git history for security risks

Retrieve security findings from Google Cloud Security Command Center for initial assessment. Filter active vulnerabilities, threats, and external exposures, inspect one finding’s full details, or group counts by category to understand the reported risks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Retrieving full details for a named security finding
• Listing active vulnerabilities or external exposures
• Summarizing active finding counts by category

Assess Web3 vulnerability findings before submission by checking scope, reproducibility, prerequisites, and attack costs. Organize the root cause, measurable impact, working proof of concept, and proposed fix into an Immunefi report, with examples for comparison.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether a finding is ready for submission
• Drafting an Immunefi vulnerability report
• Reviewing reproduction code and measurable impact

Use grep text searches to locate Solidity code that needs security review. Ten search groups, priority tiers, and protocol-specific patterns help organize findings and choose where to begin a deeper smart contract audit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Mapping review targets before a smart contract audit
• Searching for a specific vulnerability class
• Prioritizing suspicious code for deeper review

Examine a DeFi yield aggregator, a protocol that collects investment returns, for missing role assignments and failures caused by tiny rewards. Includes a ten-category review, reproducible test templates, and vulnerability report drafts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking reward contracts for missing role assignments
• Investigating harvest failures caused by tiny rewards
• Preparing vulnerability reproduction tests and reports

Choose and configure AI tools for Web3 security work across web applications, APIs, and Solidity contracts. Follow setup examples for reconnaissance, vulnerability validation, and proof-of-concept generation, then combine automated findings with manual review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing AI tools for a security testing target
• Automating web application and API reconnaissance
• Preparing Solidity checks and proof-of-concept code

Provides a reference for reviewing DeFi smart contracts, programs that manage blockchain transactions. It organizes vulnerability types with causes, code examples, search patterns, and fixes to help investigate accounting, permissions, boundary conditions, and pricing logic.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking for accounting inconsistencies and missing permission checks
• Comparing normal and alternative code paths
• Reviewing deadline and array boundary conditions

Develop security design improvements from vulnerability reports, incident documents, source code, or scan results. Compare architectural options with before-and-after diagrams, engineering tradeoffs, and migration plans to support a concrete design decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find structural causes shared by several vulnerabilities
• Compare security architecture options and costs
• Explain proposed changes with before-and-after diagrams

Run an AI vulnerability scan on uncommitted changes, changes against main, or an entire codebase. Filter candidate files, investigate potential security issues, and review findings with severity ratings, with options to revalidate and export results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking uncommitted changes for vulnerabilities
• Reviewing security issues in changes against main
• Scanning an existing codebase

Find other occurrences of a known bug across a codebase by tracing its root cause. Gradually broaden search patterns, assess matching candidates, assign severity, and document findings with rules to help prevent recurrence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding similar issues after discovering a vulnerability
• Building CodeQL or Semgrep queries from a known bug
• Checking whether similar code shares the same root cause

Verify a reported security bug by tracing inputs, checking attacker capabilities, and examining existing protections. Produces a documented TRUE POSITIVE or FALSE POSITIVE verdict for each finding, with deeper verification for complex cases.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether a reported vulnerability is real
• Verifying the conditions needed to exploit a finding
• Reviewing suspected false positives

Build a documented understanding of unfamiliar code before a security audit. It records function assumptions, guarantees, dependencies, and open questions, producing a dossier and individual function notes to support later vulnerability analysis.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understanding unfamiliar code before an audit
• Mapping dependencies for threat modeling
• Preparing background notes for an architecture review

Reviews Algorand smart contracts written in TEAL or PyTeal for 11 vulnerability patterns. Produces a complete coverage table and findings with code references, severity ratings, and suggested fixes, with optional automated checks using Tealer.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Security checks before an Algorand contract audit
• Reviewing TEAL or PyTeal transaction validation
• Verifying fixes for reported vulnerabilities

Evaluate older Wi-Fi clients and embedded devices for KRACK and FragAttacks vulnerabilities. Covers test suites, likely patch status, practical impact, and reporting findings by device, firmware version, and vulnerability identifier.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing older Wi-Fi clients
• Reviewing IoT firmware patch status
• Distinguishing KRACK and FragAttacks impacts

Get started with vulnerability review through a guided practice target, from threat modeling to scanning and triage. Ask questions about the pipeline and receive answers grounded in its documentation and source, with references and a next command.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Learn the vulnerability review workflow
• Try a first scan on the bundled practice target
• Find commands with supporting documentation