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
Tools/GitHubGitHub/jkakavas/cve-2022-0778-poc
Vulnerability AnalysisExploitationFuzzingPenetration Testing
GitHubjkakavas/cve-2022-0778-poc

CVE-2022-0778-POC

Remote proof-of-concept for CVE-2022-0778 that injects a crafted certificate into a TLS handshake to trigger the OpenSSL BN_mod_sqrt() denial-of-service vulnerability.

View Repository
113494 years agoNot yet reviewed
Share

A simple remote triggering POC for CVE-2022-0778

Why

While trying to validate whether server implementations on our side where/are vulnerable to CVE-2022-0778, it proved extremely cumbersome to do so remotely. Instructions to create maliciously crafted certificates to trigger the parsing bug in BN_nod_sqrt() have been around for a while now but the main issue is that most client implementations would try to parse the client certificate in order to use it in the TLS handshake. This in turn meant, that

  • if the implementation was vulnerable the bug would be triggered and the client consume 100% and stall.
  • if the implementation was not vulnerable, the certificate could not be parsed and client would, rightfully so, exit.

What

What was actually needed, was to be able to inject a message in the TLS handshake so that we can replace the contents of the Certificate message that the client sends to the server in response to the CertificateRequest message.

How

This depends on tlslite-ng and overrides the TLSConnection._clientKeyExchange method so that during a TLS handshake with a possibly vulnerable server:

  1. We send a ClientHello message as we would normally do
  2. We consume the ServerHelloMessage and check if it contains a CertificateRequest
  3. If it does, we construct an arbitrary Certificate message, loading the DER encoded crafted certificate from disk
  4. Send the crafted message to the server and expect it will parse it, possibly triggering CVE-2022-0778

The crafted.crt is created based on the instructions in https://github.com/drago-96/CVE-2022-0778#using-asn1-templates, feel free to recreate this if you wish so.

Usage

usage: main.py [-h] [--server SERVER] [--port PORT]

Parameters

optional arguments:
  -h, --help       show this help message and exit
  --server SERVER  Name of the server to connect for the TLS handshake,
                   defaults to "localhost"
  --port PORT      Port where server listens for TLS connections, defaults to
                   "443"
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.

    851
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    538
  • 3

    ARTEX

    baarai/artex

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

    420
  • 4

    redforge

    cybersecurity91/redforge

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

    357
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    297
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    280

Explore all tools

Browse our collection of tools

View all tools →