Big Iq Centralized ManagementApplication · F5

CVE-2017-6152

MEDIUM · 6.7 CVSS v3.0 Published 2018-03-08
Fix available
A fix is available. Upgrade to after 5.2.0 or later.
See remediation →
69/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
A local user on F5 BIG-IQ Centralized Management 5.1.0-5.2.0 with the Access Manager role has privileges to change the passwords of other users on the system, including the local admin account password.

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

F5 BIG-IQ Centralized Management versions 5.1.0 through 5.2.0 contain a privilege escalation vulnerability where users assigned the Access Manager role have unauthorized ability to change passwords for any user account on the system, including the admin account. This represents an authorization bypass allowing standard users to escalate to administrator privileges.

MitigationUpgrade BIG-IQ Centralized Management to a version beyond 5.2.0 where F5 has addressed this authorization flaw, and review user role assignments to ensure only necessary personnel hold privileged roles.

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 Iq Centralized ManagementApplication
Affected:>= 5.1.0, <= 5.2.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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. Confirm BIG-IQ Centralized Management is present
    Identify if F5 BIG-IQ Centralized Management is installed on the system. This is typically visible on the product login page or through F5 system inventory. Check for the characteristic BIG-IQ login interface which differs from standard BIG-IP.
    Affected if F5 BIG-IQ Centralized Management software is installed on the system
  2. Determine installed BIG-IQ version
    Access the BIG-IQ web interface and navigate to System > Software Management > Images, or use the command line and run 'tmsh show sys version' to display the exact installed version number.
    Affected if The installed version number is 5.1.0, 5.1.1, 5.1.2, 5.1.3, 5.1.4, 5.2.0, or any version between 5.1.0 and 5.2.0 inclusive
  3. Identify users with Access Manager role
    In the BIG-IQ web interface, go to System > Users > Role Assignments and review the list of users and their assigned roles. Look specifically for any user accounts assigned the Access Manager role.
    Affected if One or more user accounts are assigned the Access Manager role
  4. Review recent password modification events
    Examine the system audit logs at System > Logs > Audit for any password change events, particularly those targeting the admin account or other privileged accounts. Check if these were performed by users with Access Manager role.
    Affected if Password changes for admin or privileged accounts were performed by users holding only the Access Manager role

You are affected if BIG-IQ Centralized Management versions 5.1.0 through 5.2.0 is installed AND any user accounts are assigned the Access Manager role, as this combination allows unauthorized password changes and privilege escalation.

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.

From vendor data
Upgrade available Upgrade to a release after 5.2.0
Interim mitigation

Upgrade BIG-IQ Centralized Management to a version beyond 5.2.0 where F5 has addressed this authorization flaw, and review user role assignments to ensure only necessary personnel hold privileged roles.

Fix this in Big Iq Centralized Management Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6152 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6152 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