security: rate limiting on auth endpoints (F-01/F-02)#93
Merged
Conversation
…/05/09)
F-01 — API key brute-force protection: per-IP failure counter in auth.py
tracks failed attempts in a 60s sliding window; returns 429 + Retry-After
after 20 failures from the same IP.
F-02 — Login brute-force protection: @limiter.limit("10/minute; 30/hour")
on POST /api/v1/auth/login via flask-limiter 4.1.1 (added to requirements.txt,
Limiter instance in extensions.py, init_app() in create_app()).
F-05 — Webhook exemption documented with explicit IMPORTANT comment warning
future developers that new webhook handlers must implement their own auth.
F-09 — rpcbind service and socket unit disabled on LXC CT101 (pve-node1);
port 111 confirmed closed via nmap from Kali VM.
0af0a3a to
ab7ac89
Compare
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #92. Fixes the two HIGH-severity findings from the 2026-03-16 internal Kali pentest.
Test plan