Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
zhaoxuya520/competition-ad-certificate-abuseCriptografia e Web3

competition-ad-certificate-abuse

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for AD CS, certificate templates, enrollment rights, EKUs, SAN controls, PKINIT, certificate mapping, and cert-based privilege paths. Use when the user asks about ESC-style abuse, certificate templates, enrollment agents, E⁩

v2026.9.22-cab634b3 instalações+3 em 7 dias44,8 mil EstrelasMITsincronizado ontem

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-ad-certificate-abuse

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
fzk2OAX9PI…/VXQ+2Dg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacoteb8dce929…18ff213f
b8dce9299c79…b66d18ff213f3 arquivos · ⁦2.0 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-ad-certificate-abuse@cab634b

Este item ainda não foi escrito no seu idioma, então aparece em English.

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive identity edge is certificate-based and the hard part is proving how a template or CA policy turns into accepted privilege.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Identify the CA, template, enrolling principal, and accepting service before diving into every certificate detail.
  2. Separate template enrollability from cert-based authentication or privilege acceptance.
  3. Record EKUs, subject or SAN controls, issuance requirements, enrollment rights, and mapping behavior in compact blocks.
  4. Tie the issued cert to one accepted path: PKINIT, Schannel, LDAPS, WinRM, or another mapped service.
  5. Reproduce the smallest certificate issuance-to-acceptance chain that yields the decisive privilege.

Workflow

1. Map CA And Template Trust

  • Record CA configuration, template name, enrollment permissions, manager approval, authorized signatures, EKUs, subject requirements, and SAN behavior.
  • Note whether the path depends on alternate subject names, UPN, DNS names, enrollment agent behavior, or template supersedence.
  • Keep principal, template, and issuance policy tied together.

2. Prove Cert-To-Privilege Acceptance

  • Show how the issued certificate is mapped or accepted: PKINIT, smartcard logon, Schannel auth, service mapping, or explicit certificate mapping.
  • Record serial, subject, SAN, EKU, validity, and the exact service or domain edge that accepts it.
  • Distinguish certificate issuance from the separate step where privilege is actually granted.

3. Reduce To The Decisive Abuse Chain

  • Compress the path to the smallest sequence: enrollment right or misconfig -> issued cert -> accepted mapping -> resulting privilege.
  • State clearly whether the weakness lives in template config, CA policy, mapping logic, relay path, or enrollment rights.
  • If the task is really about delegation or ticket transformation after PKINIT, switch back to the tighter Kerberos skill.

Read This Reference

  • Load references/ad-certificate-abuse.md for the AD CS checklist, template checklist, and evidence packaging.

What To Preserve

  • CA names, template names, rights, EKUs, issuance flags, SAN controls, and mapping details
  • Issued certificate fields, serials, subjects, SANs, and the accepting service or logon path
  • The smallest reproducible enrollment-to-privilege chain

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.9.22-cab634b13 de nov. de 2026cab634bb8dce929Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login