dbcve.org
Managed File Transfer Platform ServerApplication · Tibco

CVE-2020-9411

CRITICAL · 9.8 CVSS v3.1 Published 2020-06-09
Fix available
A fix is available. Upgrade to after 7.1.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
The file transfer component of TIBCO Software Inc.'s TIBCO Managed File Transfer Platform Server for IBM i contains a vulnerability that theoretically allows an attacker to perform unauthorized network file transfers to and from the file system accessible to the affected component. This vulnerability is exploitable when the configuration option 'Require Node Resp' is set to 'No'. In the event of a successful exploit, the attacker could theoretically read and write any file on the file system accessible to the affected component, thus fully affecting the confidentiality, integrity, and availability of the operating system hosting the deployment of the affected system. Affected releases are TIBCO Software Inc.'s TIBCO Managed File Transfer Platform Server for IBM i: versions 7.1.0 and below, version 8.0.0.

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

A file transfer vulnerability in TIBCO Managed File Transfer Platform Server for IBM i allows unauthorized network file transfers when the configuration option 'Require Node Resp' is set to 'No', enabling an attacker to read and write any file accessible to the affected component.

MitigationEnable the 'Require Node Resp' configuration option to require node authentication and prevent unauthorized file system access.

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
Managed File Transfer Platform ServerApplication
Affected:<= 7.1.0= 8.0.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. Confirm IBM i platform
    Verify that the installed TIBCO Managed File Transfer product is the Platform Server running on IBM i (AS/400) operating system. This vulnerability only affects the IBM i platform variant.
    Affected if The product is running on any platform other than IBM i (the vulnerability is specific to IBM i)
  2. Identify installed version
    Locate the TIBCO Managed File Transfer Platform Server version information in the product installation or through its administrative interface. Compare the version number against the affected ranges: versions 7.1.0 and earlier, or version 8.0.0.
    Affected if The installed version is 7.1.0 or earlier, or exactly 8.0.0
  3. Check Require Node Resp configuration
    Access the TIBCO MFT Platform Server configuration settings (typically found in the IBM i configuration panels or configuration files) and locate the 'Require Node Resp' option. Verify whether it is set to 'No' or disabled.
    Affected if The 'Require Node Resp' option is set to 'No' (disabled)
  4. Verify network accessibility
    Confirm that the MFT Platform Server has network connectivity and is accepting file transfer requests. Check if the file transfer service port is exposed to untrusted networks.
    Affected if The MFT service is network-accessible from untrusted locations

The environment is affected if running TIBCO MFT Platform Server on IBM i with a version <= 7.1.0 or = 8.0.0, and the 'Require Node Resp' configuration is set to 'No'.

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 a release after 7.1.0
Interim mitigation

Enable the 'Require Node Resp' configuration option to require node authentication and prevent unauthorized file system access.

Recommended fix Moderate confidence
  1. Locate the configuration option 'Require Node Resp' in the TIBCO Managed File Transfer Platform Server for IBM i administrative interface or configuration files
  2. Change the 'Require Node Resp' setting from 'No' to 'Yes'
  3. Restart the affected TIBCO Managed File Transfer Platform Server service to apply the configuration change
  4. Verify that the configuration change was applied successfully by checking the server status and reviewing audit logs
Caveat Enabling 'Require Node Resp' may require corresponding changes to node/client configurations that expect unauthenticated file transfers; test thoroughly in a non-production environment before deploying to production

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

Fix this in Managed File Transfer Platform Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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