Big Iq Centralized ManagementApplication · F5
CVE-2024-47139
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 · uneditedA stored cross-site scripting (XSS) vulnerability exists in an undisclosed page of the BIG-IQ Configuration utility that allows an attacker with the Administrator role to run JavaScript in the context of the currently logged-in user. 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 · moderate confidenceStored XSS vulnerability in BIG-IQ Configuration utility where an attacker with Administrator role can inject malicious JavaScript that executes when other users view the undisclosed affected page. The script runs in the context of the currently logged-in user, enabling session hijacking or privilege escalation.
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
= 8.2.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
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify installed BIG-IQ versionAccess the BIG-IQ web interface and navigate to System > Software Management > ISO Image, or run 'tmsh show sys version' via SSH to confirm the exact installed versionAffected if The installed version is exactly 8.2.0 (note: other versions may also be affected, compare to vendor advisory)
-
Identify Administrator role usersNavigate to System > Users > User List in the BIG-IQ Configuration utility and review all users assigned the Administrator roleAffected if There are Administrator accounts that are unexpected, newly created, or belong to untrusted personnel
-
Inspect configuration pages for malicious scriptsReview key configuration pages (particularly any pages that allow storing HTML or script content) for unexpected script tags, inline JavaScript, or suspicious iframe elementsAffected if Any stored script tags, event handlers (onclick, onload, etc.), or JavaScript URLs are found in configuration fields that should not contain them
-
Review audit logs for XSS injection attemptsCheck System > Logs > Audit Log for entries containing typical XSS patterns such as <script, javascript:, onerror=, or HTML-encoded variants in user actionsAffected if Audit logs show Administrator users creating or modifying configuration objects containing XSS payloads
-
Check for session anomaliesReview active sessions and recent login history in System > Logs > Security Logs, looking for sessions originating from unexpected IP addresses or with unusual behavior patternsAffected if Multiple sessions are active for the same user from different IPs, or session hijacking indicators are present
A user is affected if running BIG-IQ version 8.2.0 and either Administrator role accounts have been compromised or malicious scripts are stored in configuration pages that could execute for other users viewing those pages.
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 · scopedApply F5's official patch for CVE-2024-47139 when released. Until then, restrict Administrator role access to trusted personnel only and monitor for anomalous JavaScript in configuration pages.
BIG-IQ Centralized Management 8.2.0 to latest available 8.x release (check F5 KB for specific fixed version)
- Verify current BIG-IQ version by navigating to System > Software Management > Images or running 'tmsh show sys version'
- Download the latest BIG-IQ Centralized Management release from downloads.f5.com or your authorized distribution channel
- Review the release notes for version 8.2.0 or later to confirm the XSS vulnerability (CVE-2024-47139) is addressed
- Schedule a maintenance window as upgrades may require downtime
- Create a backup of the current BIG-IQ configuration
- Upload the new ISO image to the BIG-IQ device
- Install the upgrade via the web interface (System > Software Management > ISO Image) or via TMSH: 'install sys software iso <filename>'
- Verify the upgrade completed successfully and the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Big Iq Centralized Management
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2024-47139 — 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-47139 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