CVE-2023-29005
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFlask-AppBuilder versions before 4.3.0 lack rate limiting which can allow an attacker to brute-force user credentials. Version 4.3.0 includes the ability to enable rate limiting using `AUTH_RATE_LIMITED = True`, `RATELIMIT_ENABLED = True`, and setting an `AUTH_RATE_LIMIT`.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFlask-AppBuilder versions before 4.3.0 do not implement rate limiting on authentication endpoints, allowing attackers to repeatedly attempt credential combinations through brute-force attacks against the login mechanism.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Flask-AppBuilder versionRun 'pip show flask-appbuilder' or import the package and print its versionAffected if version is below 4.3.0
-
Verify AUTH_RATE_LIMITED configurationInspect your Flask config file (config.py) or application configuration for AUTH_RATE_LIMITED settingAffected if AUTH_RATE_LIMITED is not set to True or is missing
-
Verify RATELIMIT_ENABLED configurationInspect your Flask config file (config.py) or application configuration for RATELIMIT_ENABLED settingAffected if RATELIMIT_ENABLED is not set to True or is missing
-
Verify AUTH_RATE_LIMIT configurationInspect your Flask config file (config.py) or application configuration for AUTH_RATE_LIMIT settingAffected if AUTH_RATE_LIMIT is not defined or set to a permissive value
If Flask-AppBuilder version is below 4.3.0 AND rate limiting is not properly configured (AUTH_RATE_LIMITED, RATELIMIT_ENABLED, and AUTH_RATE_LIMIT), the environment is vulnerable to brute-force attacks on authentication endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.3.0
Upgrade to Flask-AppBuilder 4.3.0 or later and enable rate limiting by setting AUTH_RATE_LIMITED = True, RATELIMIT_ENABLED = True, and configuring AUTH_RATE_LIMIT with appropriate thresholds.
Flask-AppBuilder >= 4.3.0
- Upgrade Flask-AppBuilder to version 4.3.0 or later using pip: pip install flask-appbuilder>=4.3.0
- In your configuration file (config.py or equivalent), add or update the following settings: Set AUTH_RATE_LIMITED = True to enable authentication rate limiting
- Set RATELIMIT_ENABLED = True to enable the rate limiting extension
- Set AUTH_RATE_LIMIT to specify the rate limit (example: AUTH_RATE_LIMIT = '5 per 15 minutes' or similar format supported by Flask-Limiter)
- Restart your Flask application to apply the new configuration
- Verify rate limiting is active by testing failed authentication attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29005 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data