How fportantier/vulpy works
Vulpy is a Flask/SQLite security-training lab with paired BAD and GOOD implementations. A browser user reaches each version’s Flask app, which dispatches to route modules; login and MFA use authentication/session services, while post pages and API routes read or publish posts. The README also identifies CSP and TLS capabilities, and the tree includes standalone cryptography/security utilities. Some unsampled modules are represented from the tree and README; their internal calls are not inferred.
Main entry points: bad/vulpy.py BAD Flask app · good/vulpy.py GOOD Flask app · bad/mod_user.py BAD user routes · good/mod_user.py GOOD user routes
Components 33
Web apps
- BAD Flask app
bad/vulpy.py - GOOD Flask app
good/vulpy.py - BAD hello page
bad/mod_hello.py - GOOD hello page
good/mod_hello.py
Identity and MFA
- BAD user routes
bad/mod_user.py - GOOD user routes
good/mod_user.py - BAD user service
bad/libuser.py - GOOD user service
good/libuser.py - BAD sessions
bad/libsession.py - GOOD sessions
good/libsession.py - BAD MFA routes
bad/mod_mfa.py - GOOD MFA routes
good/mod_mfa.py - BAD MFA service
bad/libmfa.py - GOOD MFA service
good/libmfa.py - BAD user database
bad/db_init.py - GOOD user database
good/db_init.py
Posts and API
- BAD post routes
bad/mod_posts.py - GOOD post routes
good/mod_posts.py - BAD post service
bad/libposts.py - GOOD post service
good/libposts.py - BAD API routes
bad/mod_api.py - GOOD API routes
good/mod_api.py - BAD API service
bad/libapi.py - GOOD API service
good/libapi.py - BAD post database
bad/db_init.py - GOOD post database
good/db_init.py
Security controls
- BAD CSP
bad/mod_csp.py - GOOD CSP
good/mod_csp.py - BAD TLS server
bad/vulpy-ssl.py - GOOD TLS server
good/vulpy-ssl.py
Security utilities
- Crypto utilities
utils - Brute-force tools
utils/httpbrute.py
Other components
- Browser user
Connections 38
- Browser user → BAD Flask app: uses
- Browser user → GOOD Flask app: uses
- BAD Flask app → BAD user routes: registers
bad/vulpy.py - BAD Flask app → BAD post routes: registers
bad/vulpy.py - BAD Flask app → BAD MFA routes: registers
bad/vulpy.py - BAD Flask app → BAD API routes: registers
bad/vulpy.py - BAD Flask app → BAD CSP: registers
bad/vulpy.py - BAD Flask app → BAD hello page: registers
bad/vulpy.py - GOOD Flask app → GOOD user routes: registers
good/vulpy.py - GOOD Flask app → GOOD post routes: registers
good/vulpy.py - GOOD Flask app → GOOD MFA routes: registers
good/vulpy.py - GOOD Flask app → GOOD API routes: registers
good/vulpy.py - GOOD Flask app → GOOD CSP: registers
good/vulpy.py - GOOD Flask app → GOOD hello page: registers
good/vulpy.py - BAD Flask app → BAD sessions: loads
bad/vulpy.py - GOOD Flask app → GOOD sessions: loads
good/vulpy.py - BAD user routes → BAD user service: authenticates
bad/mod_user.py - BAD user routes → BAD sessions: creates session
bad/mod_user.py - BAD user routes → BAD MFA service: validates OTP
bad/mod_user.py - GOOD user routes → GOOD user service: authenticates
good/mod_user.py - GOOD user routes → GOOD sessions: creates session
good/mod_user.py - GOOD user routes → GOOD MFA service: validates OTP
good/mod_user.py - BAD MFA routes → BAD MFA service: manages MFA
bad/mod_mfa.py - GOOD MFA routes → GOOD MFA service: manages MFA
good/mod_mfa.py - BAD post routes → BAD post service: serves posts
bad/mod_posts.py - GOOD post routes → GOOD post service: serves posts
good/mod_posts.py - BAD API routes → BAD API service: creates keys
bad/mod_api.py - BAD API routes → BAD post service: reads and writes
bad/mod_api.py - BAD API routes → BAD user service: authenticates
bad/mod_api.py - GOOD API routes → GOOD API service: creates keys
good/mod_api.py - GOOD API routes → GOOD post service: reads and writes
good/mod_api.py - GOOD API routes → GOOD user service: authenticates
good/mod_api.py - BAD user service → BAD user database: reads and writes
- BAD MFA service → BAD user database: reads and writes
- BAD post service → BAD post database: reads and writes
- GOOD user service → GOOD user database: reads and writes
- GOOD MFA service → GOOD user database: reads and writes
- GOOD post service → GOOD post database: reads and writes