Big Ip Policy Enforcement ManagerApplication · F5
CVE-2019-6628
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 · uneditedOn BIG-IP PEM 14.1.0-14.1.0.5 and 14.0.0-14.0.0.4, under certain conditions, the TMM process may terminate and restart while processing BIG-IP PEM traffic with the OpenVPN classifier.
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 confidenceIn BIG-IP PEM 14.1.0-14.1.0.5 and 14.0.0-14.0.0.4, under specific conditions involving the OpenVPN classifier, the TMM (Traffic Management Microkernel) process can terminate and restart unexpectedly, causing denial of service for handled traffic.
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 Policy Enforcement ManagerApplication
>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify BIG-IP PEM is deployedConfirm the F5 BIG-IP Policy Enforcement Manager (PEM) module is installed on the systemAffected if PEM module is not present, the vulnerability does not apply
-
Check the BIG-IP versionRun 'tmsh show sys version' or check the BIG-IP version information to identify the installed software versionAffected if The installed version falls within 14.0.0-14.0.0.4 or 14.1.0-14.1.0.5
-
Identify if OpenVPN classifier is configuredReview PEM policy configurations to determine if any classification rules for OpenVPN traffic are defined or enabledAffected if OpenVPN classification rules or policies are actively configured on the PEM module
-
Check for TMM crash logsExamine /var/log/ltm and TMM core dump files for unexpected TMM process terminations or restartsAffected if TMM process crashes or unexpected restarts are present in logs, particularly when OpenVPN traffic is being handled
The environment is affected if BIG-IP PEM is running a version between 14.0.0 and 14.0.0.4 or between 14.1.0 and 14.1.0.5 and the OpenVPN classifier is actively configured or processing traffic.
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 dataApply the appropriate F5 hotfix (14.1.0.6 or 14.0.0.5) or upgrade to 15.1.0 or later to resolve this DoS vulnerability.
Fix this in Big Ip Policy Enforcement Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6628 — 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-2019-6628 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