Big Ip Next Central ManagerApplication · F5
CVE-2024-37028
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 · uneditedBIG-IP Next Central Manager may allow an attacker to lock out an account that has never been logged in. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
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 confidenceBIG-IP Next Central Manager contains a flaw in its account lockout mechanism that allows an attacker to lock out user accounts that have never been logged into. An attacker can likely exploit this by triggering the lockout feature (e.g., through repeated failed authentication attempts or API calls) on accounts that exist but have never been used, permanently preventing the legitimate user from ever accessing their account.
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
Big Ip Next Central ManagerApplication
>= 20.1.0, < 20.2.1CVSS 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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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.
-
Confirm F5 BIG-IP Next Central Manager is deployedIdentify systems running F5 BIG-IP Next Central Manager in your environment. Check installed software inventory or network scans for this product.Affected if The product is present in the environment.
-
Check installed version against affected rangeLocate the installed version of BIG-IP Next Central Manager (typically available via the management interface, system diagnostics, or version lookup command). Compare it to the affected range: >= 20.1.0 and < 20.2.1.Affected if The installed version falls within 20.1.0 through 20.2.0.
-
Identify existing user accountsAccess the BIG-IP Next Central Manager administrative interface or user directory to enumerate all user accounts configured in the system.Affected if User accounts exist in the system.
-
Check for accounts never logged intoReview user account properties to identify any accounts that have logged in timestamp records showing they have never been used. This may be visible in user management panels, audit logs, or account metadata.Affected if There are user accounts that have never been logged into.
-
Review account lockout configurationExamine the account lockout policy settings in BIG-IP Next Central Manager to understand the lockout threshold, duration, and trigger mechanisms configured in the system.Affected if Account lockout is enabled with a low threshold or no exclusion for never-logged-in accounts.
You are likely affected if BIG-IP Next Central Manager version 20.1.0 through 20.2.0 is installed and user accounts that have never been logged into exist in the system.
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 · scoped20.2.1
Implement proper validation in the account lockout logic to exclude never-logged-in accounts from standard lockout rules, or apply rate limiting on lockout-triggering mechanisms to prevent abuse.
20.2.1 or later
- Verify the current BIG-IP Next Central Manager version is between 20.1.0 and 20.2.0 (exclusive) using the management interface or CLI
- Schedule a maintenance window for the upgrade procedure
- Download BIG-IP Next Central Manager version 20.2.1 or later from my.f5.com
- Back up the current configuration following F5 backup best practices
- Upgrade BIG-IP Next Central Manager to version 20.2.1 or later
- Verify the upgrade completed successfully and the service is operational
- Confirm the account lockout vulnerability is resolved by testing with a new unused account
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Big Ip Next Central Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37028 — 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-2024-37028 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