Big Ip Access Policy ManagerApplication · F5
CVE-2016-3687
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 · uneditedOpen redirect vulnerability in F5 BIG-IP APM 11.2.1, 11.4.x, 11.5.x, and 11.6.x before 11.6.0 HF6 and Edge Gateway 11.2.1, when using multi-domain single sign-on (SSO), allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a base64-encoded URL in the SSO_ORIG_URI parameter.
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 confidenceOpen redirect vulnerability in F5 BIG-IP APM and Edge Gateway allows remote attackers to redirect users to arbitrary websites via a base64-encoded URL in the SSO_ORIG_URI parameter when multi-domain single sign-on (SSO) is enabled. The application does not validate the encoded URL before performing the redirect, enabling phishing attacks.
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
= 11.2.1= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 11.6.0
Big Ip Edge GatewayWeb browser
= 11.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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/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.
-
Identify installed BIG-IP APM or Edge Gateway versionUse the command 'tmsh show sys version' or check the BIG-IP web UI dashboard to display the installed version numberAffected if The version matches any of these: 11.2.1, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, or 11.6.0
-
Verify if multi-domain SSO is enabledAccess the BIG-IP Configuration Utility and navigate to Access Policy > SSO Configuration, or use tmsh to list the APM SSO settings: 'tmsh list apm sso'Affected if Multi-domain single sign-on configuration exists and is active on the APM or Edge Gateway
-
Check for presence of SSO_ORIG_URI parameter in access logsReview recent access and APM logs for requests containing the parameter 'SSO_ORIG_URI' - search using 'grep SSO_ORIG_URI /var/log/apm*' or review logs via the Configuration UtilityAffected if Requests with SSO_ORIG_URI parameter are present in the logs, indicating the vulnerable endpoint is reachable
You are affected if your BIG-IP APM or Edge Gateway version is 11.2.1 through 11.6.0 AND multi-domain SSO is enabled and accessible via the SSO_ORIG_URI parameter.
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 F5 BIG-IP APM to version 11.6.0 HF6 or later, or to a current stable release. Alternatively, disable multi-domain SSO until the patch can be applied.
Fix this in Big Ip Access Policy Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3687 — 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-2016-3687 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