CVE-2017-1789
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 V6 6.2.3 and 6.3.0 could allow an unauthenticated user to remotely execute code through unspecified methods. IBM X-Force ID: 137034.
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 V6 versions 6.2.3 and 6.3.0 contains a critical vulnerability allowing unauthenticated remote code execution through unspecified methods. The critical CVSS score of 9.8 indicates a network-exploitable flaw likely affecting a default-exposed service component.
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.1= 6.2.3.2= 6.2.3.3= 6.2.3.4= 6.2.3.5= 6.3.0= 6.3.0.1= 6.3.0.2= 6.3.0.3= 6.3.0.4= 6.3.0.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 IBM Tivoli Monitoring installationLocate the Tivoli Monitoring installation directory and look for version information files such as version.txt, README, or the itmcmd command output (e.g., /opt/IBM/ITM or C:\IBM\ITM). Run 'itmcmd version' or check the installation logs for the exact version string.Affected if The installed version matches any of: 6.2.3, 6.2.3.1, 6.2.3.2, 6.2.3.3, 6.2.3.4, 6.2.3.5, 6.3.0, 6.3.0.1, 6.3.0.2, 6.3.0.3, 6.3.0.4, or 6.3.0.5.
-
Check Tivoli Monitoring services statusOn Windows, open Services and look for IBM Tivoli Monitoring services. On Unix/Linux, run 'ps -ef | grep itm' or check /etc/init.d for itm scripts. Identify which components are running.Affected if Any Tivoli Monitoring component is running on an affected version.
-
Identify network-exposed interfacesReview firewall rules, network configuration, and Tivoli Monitoring service bindings. Use 'netstat -an' or 'ss -tuln' to identify listening ports associated with Tivoli (commonly ports 1920, 3661, 5555, or custom TEPS ports).Affected if The Tivoli Monitoring service listener is bound to a network-accessible IP address rather than localhost only.
-
Verify TEPS or portal server exposureCheck if the Tivoli Enterprise Portal Server (TEPS) or portal server is enabled and accessible over the network. Inspect configuration files (e.g., TEPS configuration in KFWENV or similar) for network binding settings.Affected if TEPS or portal server is exposed on a reachable network interface.
-
Review SOAP HTTP service exposureInspect Tivoli Monitoring SOAP HTTP service configuration (commonly runs on ports like 1920 or 3661). Check if unauthenticated SOAP endpoints are reachable. Review logs for any unauthorized access attempts.Affected if SOAP HTTP service accepts unauthenticated requests from network addresses.
Your environment is affected if IBM Tivoli Monitoring version 6.2.3 through 6.3.0.5 is installed and any of its services are network-exposed.
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.
dbcve · scopedApply vendor patches as soon as available; until then, isolate affected systems from untrusted networks and disable unnecessary network exposure of Tivoli Monitoring services.
IBM Tivoli Monitoring 6.3.0 Fix Pack 2 or later (verify with IBM security bulletin)
- Check IBM Support for the specific security bulletin related to CVE-2017-1789 (IBM X-Force ID: 137034)
- Review the full list of affected versions (6.2.3, 6.2.3.1, 6.2.3.2, 6.2.3.3, and 6.3.0) in the official IBM security notice
- Identify the recommended fixed version or patch from IBM's documentation
- Plan and schedule the upgrade during a maintenance window
- Before upgrading, backup all critical configurations and data
- Test the upgrade in a non-production environment first
- Apply the upgrade following IBM's standard Tivoli Monitoring upgrade procedures
- Verify the installation and test that the code injection vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1789 — 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-1789 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