CVE-2018-5434
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 TIBCO Designer component of TIBCO Software Inc.'s TIBCO Runtime Agent, and TIBCO Runtime Agent for z/Linux contains vulnerabilities wherein a malicious user could perform XML external entity expansion (XXE) attacks to disclose host machine information. Affected releases are TIBCO Software Inc.'s TIBCO Runtime Agent: versions up to and including 5.10.0, and TIBCO Runtime Agent for z/Linux: versions up to and including 5.9.1.
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 TIBCO Designer component contains an XXE (XML External Entity) vulnerability that allows malicious XML input with external entity references to be processed, enabling disclosure of host machine file system information. The XML parser fails to disable external entity processing, allowing attackers to craft malicious XML that references local files or internal resources.
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<= 5.9.1<= 5.10.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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify TIBCO Runtime Agent versionLocate the TIBCO Runtime Agent installation directory and check the version manifest or version file. On Windows this is typically in the TIBCO home directory under 'tibco' or check the 'TIBCO_HOME' environment variable. Run 'tibversion' or check ' TRA_version' file if available.Affected if The installed version is 5.9.1 or earlier, or 5.10.0 or earlier.
-
Confirm TIBCO Designer component is presentCheck if the TIBCO Designer application or design-time tools are installed. Look for 'designer' directory under the TIBCO installation path or check for designer-related executables or modules.Affected if TIBCO Designer component exists in the installation.
-
Verify XML processing is enabledReview TIBCO project configurations, XML-related settings, or any XML parser configurations in use. Look for XML configuration files, XSLT mappings, or any feature that processes XML input files.Affected if XML parsing, transformation, or processing features are configured or active in the environment.
-
Inspect XML parser configuration for external entity settingsExamine XML parser settings in TIBCO configuration files. Check for any custom XML parser implementations or settings files that control entity resolution. The vulnerable state is when external entity processing is not explicitly disabled.Affected if XML parsers are configured to allow external entity resolution or secure processing is not explicitly enabled.
You are affected if TIBCO Runtime Agent version is 5.9.1 or earlier (or 5.10.0 or earlier), TIBCO Designer component is installed, and XML files are processed with parsers that have external entity processing enabled.
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 TIBCO Runtime Agent versions higher than 5.10.0 (or 5.9.1 for z/Linux). Alternatively, configure XML parsers to disable external entity resolution and enable secure processing features.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5434 — 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-5434 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