CVE-2018-18810
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 · uneditedThe Administrator Service component of TIBCO Software Inc.'s TIBCO Managed File Transfer Command Center, and TIBCO Managed File Transfer Internet Server contains vulnerabilities where an authenticated user with specific privileges can gain access to credentials to other systems. Affected releases are TIBCO Software Inc.'s TIBCO Managed File Transfer Command Center: versions up to and including 7.3.2; 8.0.0; 8.0.1; 8.0.2; 8.1.0, and TIBCO Managed File Transfer Internet Server: versions up to and including 7.3.2; 8.0.0; 8.0.1; 8.0.2; 8.1.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 confidenceThe Administrator Service in TIBCO Managed File Transfer Command Center and Internet Server contains an information disclosure vulnerability allowing authenticated users with specific privileges to retrieve credentials for other systems. This enables lateral movement and privilege escalation within the environment.
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<= 7.3.2>= 8.0.0, <= 8.0.2= 8.1.0<= 7.3.2>= 8.0.0, <= 8.0.2= 8.1.0CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if TIBCO MFT Command Center or Internet Server is installedLook for TIBCO installation directories (commonly under Program Files/TIBCO or similar), or check for running processes named 'mft' or 'tibco' related services.Affected if Either TIBCO Managed File Transfer Command Center or TIBCO Managed File Transfer Internet Server is present on the system.
-
Determine the installed version of TIBCO MFTLocate version information in the product's about page, installation directory readme, or configuration files. Compare the installed version against the affected ranges: <= 7.3.2, >= 8.0.0 to <= 8.0.2, or exactly 8.1.0.Affected if The installed version falls within any of these ranges: 7.3.2 or earlier, 8.0.0 through 8.0.2, or exactly 8.1.0.
-
Verify the Administrator Service component is accessibleCheck if the Administrator Service web interface or API endpoint is exposed and accessible. This is typically accessed via the product's administration console port.Affected if The Administrator Service is accessible (running and reachable via network or localhost).
-
Confirm user access to the affected functionalityReview user account privileges within the MFT system, specifically checking if the account has the specific privileges required to retrieve credentials for other systems through the Administrator Service.Affected if An authenticated user with the relevant privilege assignment can access the credential retrieval functionality.
A user is affected if TIBCO MFT Command Center or Internet Server is installed with a version within the affected ranges AND the Administrator Service is accessible with an account that has the specific privileges to retrieve credentials.
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 dataUpgrade to a patched version as indicated by TIBCO's security advisory. Review user privilege assignments and audit access logs for any suspicious credential retrieval activities.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18810 — 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-2018-18810 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