CVE-2017-1794
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 · uneditedIBM 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.
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 · moderate confidenceIBM Tivoli Monitoring versions 6.2.3 through 6.2.3.5 and 6.3.0 through 6.3.0.7 contain a vulnerability in the TEPS (Tivoli Enterprise Portal Server) component allowing user privilege escalation. Additionally, unconstrained memory growth can lead to denial of service conditions.
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>= 6.2.3, <= 6.2.3.5>= 6.3.0, <= 6.3.0.7CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/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 installed IBM Tivoli Monitoring versionRun 'itmcmd version' or check the installation directory for version files such as <install_dir>/bin/version.txt, or use the ITM Framework杖 command 'tacmd listSystems' to query the TEPS component versionAffected if The installed version falls within 6.2.3 to 6.2.3.5 or 6.3.0 to 6.3.0.7
-
Verify TEPS component is installed and runningCheck for the TEPS process (typically named 'kfwfrag' or 'TEPS' in process lists) using commands like 'ps -ef | grep -i teps' on Unix or Task Manager/Process Explorer on Windows, or query via 'itmcmd agent -list'Affected if TEPS component is present and running on the system
-
Monitor TEPS process memory consumptionObserve memory usage of the TEPS process over time using system monitoring tools such as 'top', 'ps', or Windows Task Manager. Compare baseline memory usage to current consumptionAffected if Memory usage shows unconstrained growth or abnormally high memory consumption without release
-
Check for unexpected user privilege changesReview system audit logs and TEPS logs (typically in <install_dir>/logs/TEPS/) for unauthorized privilege modifications or role changes, and compare current user permissions against documented baselinesAffected if Unauthorized privilege escalation attempts or modifications to user roles are found in logs
A system is affected if IBM Tivoli Monitoring version 6.2.3-6.2.3.5 or 6.3.0-6.3.0.7 is installed with the TEPS component running, especially if memory growth or privilege anomalies are observed.
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 IBM Tivoli Monitoring to a version beyond 6.2.3.5 or 6.3.0.7 (or apply vendor-supplied patches), and implement monitoring for anomalous memory consumption in TEPS processes.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1794 — 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-2017-1794 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