Big Ip Advanced Firewall ManagerApplication · F5

CVE-2018-15314

MEDIUM · 6.1 CVSS v3.0 Published 2018-10-19
Fix available
A fix is available. Upgrade to after 13.1.1.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
On F5 BIG-IP AFM 13.0.0-13.1.1.1 and 12.1.0-12.1.3.6, there is a Reflected Cross Site Scripting vulnerability in undisclosed TMUI page.

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 confidence

Reflected Cross Site Scripting vulnerability in undisclosed TMUI page of F5 BIG-IP AFM versions 13.0.0-13.1.1.1 and 12.1.0-12.1.3.6. The vulnerability allows injection of malicious scripts via unsanitized user input that gets reflected in the web interface response.

MitigationApply F5-provided patches for BIG-IP AFM or upgrade to a patched version. Until patched, restrict access to TMUI to trusted networks only and monitor for exploitation attempts.

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 Advanced Firewall ManagerApplication
Affected:>= 12.1.0, <= 12.1.3.6>= 13.0.0, <= 13.1.1.1

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm BIG-IP AFM is installed
    Identify if the F5 BIG-IP Advanced Firewall Manager (AFM) module is installed on the system. This can be verified via the BIG-IP command line using 'tmsh show /sys module' or by checking the TMUI login page for AFM-specific branding.
    Affected if The system does not have BIG-IP AFM installed, this CVE does not apply.
  2. Determine installed BIG-IP version
    Retrieve the installed BIG-IP version. From the command line, run 'tmsh show /sys version' or check the version displayed on the TMUI login page. Note the full version number including build.
    Affected if The installed version falls within 12.1.0-12.1.3.6 or 13.0.0-13.1.1.1, placing the system in the affected version range.
  3. Verify TMUI is accessible
    Confirm the Traffic Management User Interface (TMUI) web management interface is reachable. Check network accessibility of port 443 or the configured TMUI listening port.
    Affected if TMUI is exposed to untrusted networks, making the reflected XSS vulnerability potentially exploitable.
  4. Review TMUI access logs for suspicious parameters
    Examine TMUI access logs (typically found in /var/log/httpxml.log or via the TMUI logging interface) for unusual query parameters or script injection patterns in requests to undisclosed pages.
    Affected if Log entries show unexpected script tags or XSS payloads in URL parameters, indicating potential exploitation attempts.

The system is affected if BIG-IP AFM is installed with a version in the ranges 12.1.0-12.1.3.6 or 13.0.0-13.1.1.1 and the TMUI interface is accessible.

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 13.1.1.1
Interim mitigation

Apply F5-provided patches for BIG-IP AFM or upgrade to a patched version. Until patched, restrict access to TMUI to trusted networks only and monitor for exploitation attempts.

Fix this in Big Ip Advanced Firewall Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-15314 — 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-2018-15314 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