dbcve.org
F5os AOperating system · F5

CVE-2024-24966

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 1.6.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
When LDAP remote authentication is configured on F5OS, a remote user without an assigned role will be incorrectly authorized.  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 confidence

In F5OS with LDAP remote authentication enabled, the system incorrectly authorizes remote users who have authenticated via LDAP but have not been assigned any role. This authorization bypass allows unauthenticated or unauthorized users to gain system access they should not have, since the system fails to properly validate role assignment before granting access.

MitigationEnsure LDAP role mapping is properly configured and verify that all remote LDAP users have explicit role assignments; also review and enforce role-based access control (RBAC) validation during the authentication process.

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
F5os AOperating system
Affected:= 1.2.0
F5os COperating system
Affected:>= 1.3.0, < 1.6.0

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify F5OS product and version
    Run 'tmsh show sys version' or access the F5OS management interface to determine if you are running F5OS A or F5OS C, and note the exact version number
    Affected if Running F5OS A version 1.2.0 OR F5OS C versions 1.3.0 through 1.5.x
  2. Verify LDAP remote authentication is enabled
    Check the F5OS configuration for remote authentication settings - typically via tmsh command 'show auth ldap' or through the management UI under User Management > Remote Authentication
    Affected if LDAP remote authentication is currently enabled on the system
  3. Review LDAP user role mappings
    Inspect LDAP role configuration via tmsh 'show auth ldap' or check the role mapping table in the F5OS management interface to identify all LDAP users and their assigned roles
    Affected if Any LDAP-authenticated users exist who have NO explicit role assignment in the role mapping configuration
  4. Check for default role assignment policy
    Examine the LDAP authentication configuration for a default role setting that may be applied to users without explicit role mapping - look for settings like 'default role' or 'fallback role' in the LDAP provider configuration
    Affected if A default or fallback role is automatically assigned to LDAP users who have no explicit role mapping

You are affected if running a vulnerable F5OS version with LDAP remote authentication enabled and any LDAP users lack explicit role assignments or the system applies a default role to unmapped users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.6.0 or later
Fixed in 1.6.0
Interim mitigation

Ensure LDAP role mapping is properly configured and verify that all remote LDAP users have explicit role assignments; also review and enforce role-based access control (RBAC) validation during the authentication process.

Recommended fix Moderate confidence

F5OS C: upgrade to 1.6.0 or later; F5OS A: upgrade to the first fixed release after 1.2.0 (contact F5 support for specific version)

  1. 1. Verify current F5OS version by running 'show system version' or checking the web UI dashboard
  2. 2. For F5OS C platform: Plan upgrade to version 1.6.0 or later
  3. 3. For F5OS A platform: Plan upgrade to the next available release after 1.2.0 that addresses this vulnerability
  4. 4. Before upgrading, backup current configuration using 'save sys config' or the web UI backup function
  5. 5. Review F5OS upgrade documentation for your platform to ensure prerequisites are met
  6. 6. Perform the upgrade during a maintenance window as the process may require system restart
  7. 7. After upgrade, verify LDAP authentication still functions correctly
  8. 8. Confirm that users without assigned roles are now properly denied access (not incorrectly authorized)
Caveat Review F5OS release notes for any configuration or behavior changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in F5os A Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24966 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24966 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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