dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2020-5898

MEDIUM · 5.5 CVSS v3.1 Published 2020-05-12
Fix available
A fix is available. Upgrade to after 15.1.0.3 or later.
See remediation →
57/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
In versions 7.1.5-7.1.9, BIG-IP Edge Client Windows Stonewall driver does not sanitize the pointer received from the userland. A local user on the Windows client system can send crafted DeviceIoControl requests to \\.\urvpndrv device causing the Windows kernel to crash.

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

The BIG-IP Edge Client Windows Stonewall driver (urvpndrv) in versions 7.1.5-7.1.9 fails to sanitize pointers received from userland. A local authenticated user can send specially crafted DeviceIoControl requests to the \\.\urvpndrv device, causing a kernel panic/crash and resulting in local denial of service.

MitigationUpgrade BIG-IP Edge Client Windows Stonewall driver to a version beyond 7.1.9 where the pointer sanitization issue has been fixed.

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
Affected:>= 11.6.1, <= 11.6.5.1>= 12.1.0, <= 12.1.5.1>= 13.1.0, <= 13.1.3.3>= 14.1.0, <= 14.1.2.5>= 15.0.0, <= 15.1.0.3
Big Ip Access Policy Manager ClientApplication
Affected:>= 7.1.5, <= 7.1.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Check if the urvpndrv.sys driver file exists
    Search for urvpndrv.sys on the Windows system. Common locations: C:\Windows\System32\drivers\urvpndrv.sys or within the F5 client installation directory (typically C:\Program Files\F5 Networks\Edge Client\). Right-click the file, select Properties, and view the Version tab to identify the file version.
    Affected if The file exists and its version falls within 7.1.5 to 7.1.9 inclusive.
  2. Check the installed F5 BIG-IP Edge Client version
    Open Windows Control Panel > Programs and Features (or Settings > Apps & Features on Windows 10/11). Look for an entry named 'F5 Networks BIG-IP Edge Client' or 'F5 Networks Edge Client' and note the version number shown.
    Affected if The installed version is between 7.1.5 and 7.1.9 inclusive.
  3. Verify if the urvpndrv driver service exists
    Open Command Prompt and run: sc query urvpndrv. This queries the Windows service configuration for the Stonewall driver. Also run: sc qc urvpndrv to see the service type and start configuration.
    Affected if The service 'urvpndrv' exists and the driver binary version is 7.1.5-7.1.9.
  4. Check F5 Access Policy Manager version if using the full APM product
    If this is a BIG-IP device rather than standalone client, access the BIG-IP web configuration utility (TMUI). Navigate to Overview > Dashboard or System > Software Management > ISO Upload to view the installed BIG-IP version. The vulnerability exists in APM modules for versions 11.6.1-11.6.5.1, 12.1.0-12.1.5.1, 13.1.0-13.1.3.3, 14.1.0-14.1.2.5, and 15.1.0-15.1.0.3.
    Affected if The BIG-IP APM version falls within any of the affected version ranges listed.

The system is affected if the urvpndrv driver or F5 Edge Client version is 7.1.5 through 7.1.9, or if the BIG-IP APM module version is within any of the affected APM version ranges.

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

Upgrade BIG-IP Edge Client Windows Stonewall driver to a version beyond 7.1.9 where the pointer sanitization issue has been fixed.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5898 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2020-5898 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