How cymmetria/ciscoasa_honeypot works
Project type and purpose
• This is a low-interaction honeypot emulating a Cisco ASA management interface and IKE endpoint.
• Written in Python, it listens on configurable HTTP(S) and IKE ports to detect CVE-2018-0101 exploitation attempts and logs interactions locally or to an hpfeeds broker.
File structure
Top-level:
• Dockerfile, docker-compose.yml → containerized deployment
• asa_server.py → HTTP(S) honeypot server
• ike_server.py → IKE/UDP honeypot server
• gencert.py → self-signed cert generation
• requirements.txt → Python dependencies
• asa/ (static assets) → HTML pages, CSS, JS used to mimic the ASA web UI
• .python-version, .gitignore, LICENSE, README.md
README for additional insights
• Configurable host, ports, SSL enablement, certificate path or auto-gen.
• Optional hpfeeds logging parameters (can be set via CLI flags or environment).
• No external database—logging is either to console/files or forwarded to an hpfeeds server.
a. Main components
1. External Network (Attacker)
2. Docker Container / Host Machine
• Web Honeypot Service (asa_server.py)
• IKE Honeypot Service (ike_server.py)
• Certificate Generator (gencert.py)
• Static Asset Store (/asa directory)
• Logging Module
3. Optional External hpfeeds Broker
b. Relationships & data flows
• Attacker → TCP/UDP network → Docker container
– → HTTP(S) port → asa_server.py
– → IKE port → ike_server.py
• asa_server.py and ike_server.py call the Logging Module to record events
• Logging Module → (optional) hpfeeds Broker → downstream logging/analysis
c. Architectural patterns & principles
– Single-host, multi-process (or multi-thread) honeypot
– Clear separation: HTTP service vs. IKE service vs. logging
– Containerized deployment for isolation and reproducibility
d. Key technologies & frameworks
– Python 3 (asyncio or built-in HTTP server)
– Docker & docker-compose
– hpfeeds (network logging protocol)
– OpenSSL (via gencert.py)
– Static web assets (HTML/CSS/JS) to mimic ASA UI