Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2013-3900-PowerShell-PoC — CVE PoC | Kitploit
Tools/GitHubGitHub/norvethil/cve-2013-3900-powershell-poc
Payload GenerationVulnerability AnalysisExploitationBinary AnalysisLearning & Education
GitHubnorvethil/cve-2013-3900-powershell-poc

CVE-2013-3900-PowerShell-PoC

CVE PoC

View Repository
Share
51331 year agoNot yet reviewed

CVE-2013-3900-PowerShell-PoC

This PoC is provided for educational and research purposes only. The author takes no responsibility for misuse or damage caused by this code.

This PowerShell script is a testing tool for simulating the attack described in CVE-2013-3900. CVE-2013-3900 concerns the Authenticode mechanism in Windows, in which the PE signature (EXE/DLL files) may contain additional data (padding) in the certificate section. In older or default Windows settings, such a modification does not invalidate the signature, allowing malicious code to be added to the file while retaining its “signed” status. By enabling EnableCertPaddingCheck=1 in the registry, the system begins to treat additional padding as a violation of integrity, rejecting such a file.

Script:

  • Opens the selected signed EXE file.
  • Adds artificial padding to the certificate section.
  • Saves a modified copy of the file.
  • Checks the signature of the original and the copy.
  • Calls the WinVerifyTrust API to see if the system (with the current settings) will accept or reject the modified file.

If protection is enabled, the modified file will be rejected (0x800B0100); if disabled, it will be accepted (0x00000000).

I use MSBuild.exe because it is a Windows system file with an embedded Authenticode signature (not a catalog signature), which allows us to directly modify its certificate section and reliably simulate the CVE-2013-3900 vulnerability. This makes the test repeatable and works on any Windows Server installation without the need to download additional files.

To run script:

CMD C:\>powershell -ExecutionPolicy Bypass -File C:\CVE-2013-3900-PoC-padding-injection.ps1

Links: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    491
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    462
  • 3

    opencti

    opencti-platform/opencti

    Open Cyber Threat Intelligence Platform

    345
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    340
  • 5

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    306
  • 6

    estorides

    grisuno/estorides

    Aggregates 99+ free OSINT sources in parallel, resolves entities into a knowledge graph, and exports STIX 2.1, MISP, or GraphML with LLM-assisted analysis.

    292

Explore all tools

Browse our collection of tools

View all tools →