dbcve.org
User IdApplication · Forcepoint

CVE-2019-6139

CRITICAL · 9.8 CVSS v3.1 Published 2019-02-07
Fix available
A fix is available. Upgrade to 1.3.0 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 User ID (FUID) server versions up to 1.2 have a remote arbitrary file upload vulnerability on TCP port 5001. Successful exploitation of this vulnerability may lead to remote code execution. To fix this vulnerability, upgrade to FUID version 1.3 or higher. To prevent the vulnerability on FUID versions 1.2 and below, apply local firewall rules on the FUID server to disable all external access to port TCP/5001. FUID requires this port only for local connections through the loopback interface.

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 User ID server versions up to 1.2 contain a remote arbitrary file upload vulnerability on TCP port 5001. An unauthenticated attacker can exploit this to upload malicious files, potentially achieving remote code execution on the affected system.

MitigationUpgrade to FUID version 1.3 or higher to remediate the vulnerability. Alternatively, apply local firewall rules to block external access to TCP/5001, allowing only loopback interface connections.

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
User IdApplication
Affected:< 1.3.0

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify Forcepoint User ID installation
    Check if Forcepoint User ID server is installed on the system by reviewing installed software, services, or process lists for Forcepoint User ID components.
    Affected if Forcepoint User ID is found running on the system.
  2. Determine installed version
    Locate and read the version information for Forcepoint User ID. This may be available via the software itself, installation directory, or system inventory tools.
    Affected if The installed version is identified as less than 1.3.0.
  3. Verify TCP port 5001 listener status
    Use netstat, ss, or similar network tools to check if TCP port 5001 is in LISTEN state on the system.
    Affected if Port 5001 is open and listening on any interface.
  4. Assess network exposure of port 5001
    Review firewall rules, binding configuration, or network scans to determine if port 5001 is accessible from external network addresses versus only localhost.
    Affected if Port 5001 is bound to non-loopback interfaces and accessible from network segments beyond localhost.

The environment is affected if Forcepoint User ID version below 1.3.0 is installed with TCP port 5001 exposed and listening on accessible network interfaces.

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 1.3.0 or later
Fixed in 1.3.0
Interim mitigation

Upgrade to FUID version 1.3 or higher to remediate the vulnerability. Alternatively, apply local firewall rules to block external access to TCP/5001, allowing only loopback interface connections.

Recommended fix High confidence

Forcepoint User ID 1.3 or higher

  1. Obtain Forcepoint User ID version 1.3 or higher from the official Forcepoint support portal or download center
  2. Stop the Forcepoint User ID (FUID) service
  3. Install or upgrade to FUID version 1.3 or higher
  4. Restart the FUID service after upgrade completes
  5. Verify the upgrade was successful by checking the installed FUID version

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

Fix this in User Id Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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