'cv' 검색 결과

Exploit the noPac vulnerability chain (CVE-2021-42278 sAMAccountName spoofing and CVE-2021-42287 KDC PAC confusion) to escalate from standard domain user to Domain Admin in Active Directory environments.

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

Turn career details into a minimal, single-page A4 resume prepared for printing or PDF export. The template organizes experience, projects, education, and skills with restrained colors, clear headings, and an optional two-column layout.

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

• Creating a single-page A4 resume
• Organizing experience and skills in two columns
• Preparing a resume for printing or PDF export

Estimate RNA velocity, the modeled direction of gene expression change, from single-cell spliced and unspliced counts. Fit models, inspect gene-level plots, visualize trajectories, and explore relative timing and associated genes while checking model limitations.

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

• Explore hypotheses about directions of cell-state change
• Inspect gene-level RNA velocity model fits
• Estimate relative cell ordering with a dynamical model

Analyze investment returns and portfolio risk using loss thresholds, average losses beyond those thresholds, and peak-to-trough declines. Combine simulated price paths with historical and hypothetical market shocks to produce a risk report and control recommendations.

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

• Examining risks behind backtest results
• Comparing portfolio losses under market shocks
• Measuring drawdowns and time to recovery

Retrieve price and trading volume data for US, Hong Kong, and Canadian stocks, ETFs, and indices through Yahoo Finance. Also gather company profiles, financial statements, dividends, and ownership data for market research and historical strategy testing.

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

• Collect historical prices across several stock markets
• Review company financial statements and ownership
• Check dividend and stock split histories

Build machine-learning trading signals from price and volume data. The workflow checks inputs, creates predictive features, and repeatedly trains on available historical data to produce bounded signals indicating predicted direction and strength.

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

• Building trading signals from price and volume data
• Comparing machine-learning models
• Testing expanding and sliding training windows

Assess whether a container can escape its isolation and reach the host during an authorized security test. Review privileges, shared mounts, Docker socket exposure, and runC vulnerabilities, then document demonstrated impact and remediation.

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

• Testing container escape within an approved scope
• Assessing the impact of privileged or hostPath workloads
• Validating controls that block container escape

Review dependency manifests and lockfiles to find outdated packages and known security vulnerabilities. Group proposed updates by version change, report current and suggested versions, and identify updates that need human review.

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

• Reviewing outdated dependencies
• Checking known vulnerabilities and update options
• Separating patch, minor, and major updates

Turn penetration test and red team results into reports for executives and technical teams. Structure findings, explain severity scores and business impact, organize evidence, and document remediation steps and retest plans.

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

• Preparing a final penetration test report
• Rewriting an executive summary for nontechnical readers
• Creating a reusable security reporting template

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

Investigate how a limited Linux account could gain root, the system administrator's privileges. The skill guides checks of permissions, scheduled tasks, services, and known vulnerabilities, while outlining evidence defenders can monitor during authorized security assessments.

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

• Assessing Linux privilege escalation paths
• Practicing privilege escalation in CTF challenges
• Reviewing sudo and scheduled task configurations

Turn validated security findings into clear bug bounty reports for HackerOne, Bugcrowd, Intigriti, or Immunefi. Provides templates, reproducible evidence structure, severity scoring guidance, and submission checks focused on demonstrated impact.

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

• Draft a report for a specific bounty platform
• Document reproducible requests and evidence
• Explain severity using demonstrated impact

Evaluate security findings before writing a bug bounty report. Check reproducibility, scope, practical impact, duplicates, and behavior across user sessions, then use submission checklists and CVSS 3.1 guidance to prepare evidence and assess severity.

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

• Deciding whether a finding is ready to report
• Rechecking access across different user sessions
• Reviewing duplicate or intended behavior

Complete security architecture overhaul for claude-flow v3. Addresses critical CVEs (CVE-1, CVE-2, CVE-3) and implements secure-by-default patterns. Use for security-first v3 implementation.

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

CVE validation domain card. Use after CVE lookup has produced applicable or candidate CVEs and red-team mode needs scoped evidence to decide whether to continue, pivot, or report.

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

Audit a Python project's installed dependencies for known CVEs by wrapping pip-audit (PyPA's official vulnerability auditor) and emitting findings in the canonical penetration-tester schema. Detects vulnerable direct AND transitive packages, normalizes pip-audit's severity output via OSV severity bands, falls back to pip list --outdated when pip-audit isn't installed, and supports requirements.txt, pyproject.toml (PEP 621), Pipfile.lock, and poetry.lock as input sources. Use when: pre-merge gate on a Python project, post-incident sweep after a PyPI compromise (e.g. ctx, request-toolbelt typosquats, ultralytics 8.3.42 compromise), SOC2 evidence collection, or inheriting an unfamiliar Python codebase. Threshold: any HIGH or CRITICAL CVE in the resolved dependency tree. MODERATE / LOW reported informationally. Trigger with: "audit python deps", "pip vulnerability scan", "check pypi packages for CVEs", "pip-audit run".

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

Audit a Node.js project's installed npm dependency tree for known CVEs by wrapping the npm audit JSON output and emitting findings in the canonical penetration-tester schema. Detects direct AND transitive vulnerabilities, normalizes npm's severity scale (info/low/moderate/ high/critical) to the shared Severity enum, and parses both v1 and v2 audit output formats so the skill works against npm 6 and npm 7+ lockfiles. Use when: pre-merge gate on a Node project, post-incident sweep after a transitive package compromise (e.g. event-stream, ua-parser, node-ipc, color.js), SOC2 vendor-management evidence collection, or auditing an inherited or acquired Node codebase. Threshold: any HIGH or CRITICAL CVE in the resolved dependency tree. MODERATE / LOW reported informationally. Trigger with: "audit npm deps", "npm vulnerability scan", "check node packages for CVEs", "npm audit".

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

Build safe, local, defensive reproductions of ALREADY-PATCHED, publicly disclosed security vulnerabilities (CVEs, vendor advisories, AI-agent incidents) for whitepapers, control testing, and education. Use this skill whenever the user wants to reproduce, demonstrate, or write up a known vulnerability or security incident — phrases like "reproduce this CVE", "build a repro for", "demonstrate the EchoLeak/Cursor/postmark-mcp issue", "show how this exploit worked", "add a reproducibility guide", or "pull the NVD/CVE details for". It fetches advisory metadata from NVD and CVE.org, confirms the issue is fixed, and produces a vulnerable-vs-patched harness that is offline, loopback-only, and uses synthetic markers. It NEVER discovers, develops, or weaponizes new zero-days and refuses any unpatched or live-target request.

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

End-to-end methodology for reproducing AND patching publicly disclosed, already-fixed vulnerabilities: sourcing the advisory and the fix commit, reading the patch diff, rebuilding a pinned offline lab, building a vulnerable-vs-patched contrast harness with proper controls, minimizing the trigger, designing and validating the fix, and writing it up as a blog post or whitepaper. Use this skill whenever the user wants to reproduce, demonstrate, understand, teach, or write about a known vulnerability or security incident: "reproduce this CVE", "build a repro for", "how did EchoLeak / Log4Shell / the postmark-mcp package actually work", "show me how this exploit worked", "write a blog post about this vulnerability", "set up a lab for CVE-XXXX", "pull the NVD/CVE/OSV details", or "make a PoC I can publish". Use it just as eagerly for the patching half: "how should this be fixed", "is this patch correct", "what would have caught this", "review this security fix", "write a regression test for this CVE", "how do I backport this", or "what's the right fix for this bug class" - even when the user never says the word "reproduce". Reach for it on vague asks like "help me understand this security advisory", "I want to write about this incident", or "can we test whether we were vulnerable" when a disclosed vulnerability is in play. This skill only handles ALREADY-PATCHED, publicly disclosed issues and refuses zero-day discovery, live targets, and weaponization.

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

Write a CV for someone moving into a new field, leading with transferable evidence instead of job titles that do not match. Use when asked to write a CV for a career change, I'm moving from teaching into product, how do I present my experience for a new industry, or my job titles don't fit the jobs I want. Produces a hybrid CV with a targeted summary and a relevant-skills section backed by achievements, a translation table from old-field language to new-field language, and an honest list of gaps with how to close them.

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

Use when drafting, updating, or reviewing an S2-XXX security bulletin on the Struts cwiki, when preparing bulletin text ahead of a CVE request, when filling a CVE record in the ASF CVE tool (cveprocess.apache.org / Vulnogram), when deciding when to publish, when publishing a bulletin and announcing it to the ASF lists, when wrapping up after the advisory mails, or when deciding how much detail about a fixed vulnerability is safe to publish.

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

Complete security architecture overhaul for claude-flow v3. Addresses critical CVEs (CVE-1, CVE-2, CVE-3) and implements secure-by-default patterns. Use for security-first v3 implementation.

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

Deep learning for single-cell analysis using scvi-tools. This skill should be used when users need (1) data integration and batch correction with scVI/scANVI, (2) ATAC-seq analysis with PeakVI, (3) CITE-seq multi-modal analysis with totalVI, (4) multiome RNA+ATAC analysis with MultiVI, (5) spatial transcriptomics deconvolution with DestVI, (6) label transfer and reference mapping with scANVI/scArches, (7) RNA velocity with veloVI, or (8) any deep learning-based single-cell method. Triggers include mentions of scVI, scANVI, totalVI, PeakVI, MultiVI, DestVI, veloVI, sysVI, scArches, variational autoencoder, VAE, batch correction, data integration, multi-modal, CITE-seq, multiome, reference mapping, latent space.

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

Dependency auditing, CVE detection, configuration security review, CVSS scoring, and prioritized vulnerability reporting

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