Updated Jul 15, 2026

Recon

Match a BIG-IP management URL to its release

Fingerprint the software version of a remote F5 BIG-IP management interface.

Python · MIT license

Agent

overview

What bigip-scanner does

Slot bigip-scanner after a port or service scan flags an F5 management URL. It stops at version ID; discovery and CVE exploit steps stay elsewhere in the graph.

Run it when you already know the host is BIG-IP and need the exact release before picking nuclei templates or manual checks. Without -v, there is no fingerprint table to match against.

Inputs are -t for the management URL and -v for the version table. Outputs are a file and folder. Prefer this over httpx or fingerprintx when you need a release string, not a generic tech hint.

source github.com/BishopFox/bigip-scanner

use cases

Where bigip-scanner fits

Pin down a BIG-IP release before testing

Fingerprint the management interface so you know the exact version, then map it to known CVEs instead of firing every exploit blindly.

Triage exposed F5 edge devices

Across an estate of edge appliances, version each BIG-IP interface to find which ones run releases with public, unpatched vulnerabilities.

Confirm a service after a port scan

Feed a host flagged as F5 by a port or service scan into bigip-scanner to confirm the appliance and capture its precise version.

Track patching with a custom version table

Supply your own version table so the scanner recognizes the releases in your environment and reports drift as devices get patched.

reference

bigip-scanner inputs and flags

4 inputs
NameTypeFlagDescription
targetSTRING-tTarget URL of the BIG-IP management interface.
version-tableFILE-vVersion table mapping resource fingerprints to releases.
allBOOLEAN-aRequest all resources instead of stopping at the first exact match.
debugBOOLEAN-dDebug mode, showing the requests and responses used to fingerprint.

Showing key inputs. bigip-scanner exposes 4 inputs in total.

example

Run bigip-scanner

bigip-scanner · command
# fingerprint a BIG-IP management URL against the version table
bigip-scanner -t https://bigip.example.com -v version-table.txt
sample output
[*] Target: https://bigip.example.com
[*] Loading version table
[*] Probing management resources
[+] Exact match: BIG-IP 15.1.5 Build 0.0.1
[*] Host: bigip.example.com
[*] Interface: https://bigip.example.com
[+] Version written for downstream CVE mapping

guidance

Choosing bigip-scanner

Use bigip-scanner once a port scan or fingerprinter such as naabu or fingerprintx has already flagged an F5 BIG-IP management interface. It versions a known appliance; it does not find hosts.

fingerprintx

General service fingerprinter across many protocols. bigip-scanner is built only for F5 BIG-IP releases.

nuclei

Runs CVE templates once you know the version. bigip-scanner supplies that version string.

httpx

Detects tech and titles broadly. bigip-scanner pins the exact BIG-IP release a broad prober only hints at.

faq

bigip-scanner questions

The running software version of a remote F5 BIG-IP management interface, derived by matching requested resources against the -v version table.

Use -a to request all resources instead of stopping at the first exact match. That helps when a partial fingerprint is ambiguous or you want a fuller comparison.

No. -d only shows the requests and responses used during fingerprinting. The matched release stays the same when the table hits.

Those tools classify services broadly. bigip-scanner matches BIG-IP management resources to a release table so you get a concrete version for CVE scope.

A host already identified as an F5 BIG-IP interface. Wire the management URL into -t after the discovery step, and supply -v with your version table.

Run bigip-scanner yourself

A host is probed by httpx to confirm a live F5 interface, then bigip-scanner fingerprints its release and writes the detected version as a queryable output.

Facts on this page come from the live Trickest tool library.