CVE-2019-11211
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 server component of TIBCO Software Inc.'s TIBCO Enterprise Runtime for R - Server Edition, and TIBCO Spotfire Analytics Platform for AWS Marketplace contains a vulnerability that theoretically allows an authenticated user to trigger remote code execution in certain circumstances. When the affected component runs with the containerized TERR service on Linux the host can theoretically be tricked into running malicious code. This issue affects: TIBCO Enterprise Runtime for R - Server Edition version 1.2.0 and below, and TIBCO Spotfire Analytics Platform for AWS Marketplace 10.4.0; 10.5.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 confidenceAuthenticated users can potentially achieve remote code execution on the host system when the TIBCO Enterprise Runtime for R (TERR) service runs in a containerized Linux environment. The vulnerability allows container escape, enabling malicious code execution beyond the container boundary.
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<= 1.2.0= 10.4.0= 10.5.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.1/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 TERR installationRun command: which terrserv or find / -name 'terrserv' 2>/dev/null to locate the TIBCO Enterprise Runtime for R server binaryAffected if TERR server binary exists on the system
-
Check TERR versionRun: terrserv --version or check the product documentation for version display command. Also check /opt/tibco/terr/VERSION or similar version file if it existsAffected if Installed version is 1.2.0 or lower
-
Verify Spotfire AWS version if applicableFor TIBCO Spotfire Analytics Platform for AWS, check the installed version via the AWS marketplace deployment documentation or check version files in the installation directoryAffected if Running version 10.4.0 or 10.5.0 on AWS
-
Confirm containerized deploymentCheck if TERR runs inside a container by running: docker ps | grep -i tibco or kubectl get pods | grep -i tibco or inspecting running processes for container runtime indicatorsAffected if TERR service is running inside a Docker or Kubernetes container
-
Check container isolation settingsInspect container security configuration: docker inspect <container_id> --format '{{.HostConfig.Privileged}}' and check for --privileged flag or excessive capabilities (--cap-add=ALL)Affected if Container runs in privileged mode or with excessive capabilities allowing container escape
You are affected if TERR version 1.2.0 or lower (or Spotfire AWS 10.4.0/10.5.0) is running in a containerized Linux environment with weak isolation controls.
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 TIBCO Enterprise Runtime for R - Server Edition to a version above 1.2.0, and TIBCO Spotfire Analytics Platform for AWS Marketplace to a version above 10.5.0. Additionally, ensure container isolation best practices are followed (least privilege, network segmentation).
- Consultation8.0 h
- Implementation16.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11211 — 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-2019-11211 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