Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
zhaoxuya520/competition-ad-certificate-abuseCriptografía y 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 instalaciones+3 en 7 días44,8 mil EstrellasMITsincronizado hace 2 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

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

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
fzk2OAX9PI…/VXQ+2Dg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paqueteb8dce929…18ff213f
b8dce9299c79…b66d18ff213f3 archivos · ⁦2.0 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-ad-certificate-abuse@cab634b

Esta entrada todavía no está escrita en tu idioma, así que aparece en 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

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.9.22-cab634b13 nov 2026cab634bb8dce929Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login