dbcve.org
Next Generation FirewallApplication · Forcepoint

CVE-2019-6143

CRITICAL · 9.1 CVSS v3.1 Published 2019-08-20
Fix available
A fix is available. Upgrade to 6.4.7 / 6.5.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Forcepoint Next Generation Firewall (Forcepoint NGFW) 6.4.x before 6.4.7, 6.5.x before 6.5.4, and 6.6.x before 6.6.2 has a serious authentication vulnerability that potentially allows unauthorized users to bypass password authentication and access services protected by the NGFW Engine. The vulnerability affects the following NGFW features when the LDAP authentication method is used as the backend authentication: IPsec VPN, SSL VPN or Browser-based user authentication. The vulnerability does not apply when any other backend authentication is used. The RADIUS authentication method is not vulnerable, for example.

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

Forcepoint NGFW versions 6.4.x before 6.4.7, 6.5.x before 6.5.4, and 6.6.x before 6.6.2 contains a critical authentication bypass vulnerability when LDAP is used as the backend authentication method, potentially allowing unauthorized access to IPsec VPN, SSL VPN, or browser-based user authentication services.

MitigationUpgrade to Forcepoint NGFW version 6.4.7, 6.5.4, or 6.6.2 or later; alternatively, migrate from LDAP to RADIUS or another non-vulnerable authentication backend.

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
Next Generation FirewallApplication
Affected:>= 6.4.0, < 6.4.7>= 6.5.0, < 6.5.4>= 6.6.0, < 6.6.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Forcepoint NGFW version
    Determine the installed version of Forcepoint NGFW through the management interface or system commands, then compare it to the affected ranges: 6.4.0 to 6.4.6, 6.5.0 to 6.5.3, or 6.6.0 to 6.6.1
    Affected if The installed version falls within any of the affected ranges (6.4.x < 6.4.7, 6.5.x < 6.5.4, or 6.6.x < 6.6.2)
  2. Verify LDAP authentication is in use
    Inspect the authentication configuration for IPsec VPN, SSL VPN, or browser-based user authentication to determine whether LDAP is configured as the backend authentication method
    Affected if LDAP is configured as the authentication backend for any of these services

You are affected if your Forcepoint NGFW version is 6.4.x before 6.4.7, 6.5.x before 6.5.4, or 6.6.x before 6.6.2 AND LDAP is used as the authentication backend for VPN or user authentication services.

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.

dbcve · scoped
Upgrade available Upgrade to 6.4.7 / 6.5.4 / 6.6.2 or later
Fixed in 6.4.76.5.46.6.2
Interim mitigation

Upgrade to Forcepoint NGFW version 6.4.7, 6.5.4, or 6.6.2 or later; alternatively, migrate from LDAP to RADIUS or another non-vulnerable authentication backend.

Recommended fix High confidence

Upgrade to Forcepoint NGFW 6.4.7, 6.5.4, or 6.6.2 depending on your current version branch

  1. Identify the currently installed Forcepoint NGFW version by checking the engine management interface or running the system version command
  2. Determine which version branch you are currently on (6.4.x, 6.5.x, or 6.6.x)
  3. Plan the upgrade to the appropriate fixed release: upgrade to 6.4.7 if on 6.4.x branch, upgrade to 6.5.4 if on 6.5.x branch, or upgrade to 6.6.2 if on 6.6.x branch
  4. Review the Forcepoint NGFW upgrade guide and release notes for your target version before initiating the upgrade
  5. Schedule a maintenance window as upgrades may require brief service interruption
  6. Download the upgrade package from the Forcepoint customer portal or official distribution channel
  7. Back up the current NGFW configuration before proceeding with the upgrade
  8. Execute the upgrade following Forcepoint's documented procedures for your specific deployment
Caveat Review release notes for any configuration or behavioral changes between your current version and the target fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Next Generation Firewall Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
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,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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