Big Ip Access Policy ManagerApplication · F5
CVE-2017-6139
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 · uneditedIn F5 BIG-IP APM software version 13.0.0 and 12.1.2, under rare conditions, the BIG-IP APM system appends log details when responding to client requests. Details in the log file can vary; customers running debug mode logging with BIG-IP APM are at highest risk.
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 confidenceIn F5 BIG-IP APM versions 13.0.0 and 12.1.2, under rare conditions the system appends internal log details to client responses, potentially exposing sensitive information from APM logs. This information disclosure occurs when the system processes certain client requests and leaks log data in the response body.
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 Access Policy ManagerApplication
= 12.1.2= 13.0.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/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.
-
Verify APM versionRun 'tmsh show /apm version' or check the BIG-IP GUI under Access Policy > Overview to confirm the installed APM versionAffected if The installed version is exactly 12.1.2 or 13.0.0
-
Confirm debug logging statusCheck the APM logging configuration by reviewing the Access Policy > Event Logs > Settings in the GUI or running 'tmsh list /apm log global' to see if debug logging is enabledAffected if Debug logging is enabled on the APM module (this increases the likelihood of sensitive data exposure in the affected versions)
-
Inspect recent access logs for sensitive dataReview APM access logs under /var/log/apm for any entries that may have been included in client response bodies, or examine recent HTTP response bodies from APM-processed requests for unexpected log contentAffected if Log entries or internal system details appear in client-facing response bodies
-
Check for anomalous response behaviorAnalyze recent client request responses from APM-protected resources, looking for unexpected text that resembles internal APM log messages or system pathsAffected if Client responses contain internal APM log details that should not be visible to end users
A user is affected if they are running APM version 12.1.2 or 13.0.0 and are experiencing log data leakage in client responses, particularly when debug logging is enabled.
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.
From vendor dataUpgrade BIG-IP APM to a patched version beyond 13.0.0 and 12.1.2. Additionally, disable debug mode logging in production unless explicitly required for troubleshooting, as this increases the risk of sensitive data exposure.
Fix this in Big Ip Access Policy Manager
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-2017-6139 — 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-2017-6139 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