CVE-2017-1789: IBM Tivoli Monitoring V6 6.2.3 and 6.3.0 could allow an unauthenticated user to remotely execute code through unspecified methods.
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.1% (FIRST EPSS); higher than 88.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
IBM 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.
- Published
- Mar 22, 2018
- Updated
- Jun 16, 2026
- EPSS
- 3.1% · 88th percentile
- CWE
- CWE-94
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.1%
CNA vs NVD score
- NVD
- 9.8
- CNA · ibm
- 9.8
- agree
CVSS:3.0/A:H/AC:L/AV:N/C:H/I:H/PR:N/S:U/UI:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ibm | tivoli monitoring | cpe:2.3:a:ibm:tivoli_monitoring |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM Tivoli Monitoring V6
- 6.2.3, 6.3.0, 6.2.3.1, 6.2.3.2, 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 … (+2)affected
Affected versions · NVD (14)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm tivoli monitoring6.2.3
- ibm tivoli monitoring6.2.3.1
- ibm tivoli monitoring6.2.3.2
- ibm tivoli monitoring6.2.3.3
- ibm tivoli monitoring6.2.3.4
- ibm tivoli monitoring6.2.3.5
- ibm tivoli monitoring6.3.0
- ibm tivoli monitoring6.3.0.1
- ibm tivoli monitoring6.3.0.2
- ibm tivoli monitoring6.3.0.3
- ibm tivoli monitoring6.3.0.4
- ibm tivoli monitoring6.3.0.5
- ibm tivoli monitoring6.3.0.6
- ibm tivoli monitoring6.3.0.7
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-7411The portal client in IBM Tivoli Monitoring (ITM) 6.2.2 through FP9, 6.2.3 through FP5, and 6.3.0 through FP6 allows remote authenticated…40Plan
- CVE-2025-3356IBM Tivoli Monitoring is vulnerable to unauthenticated file read and write operations39Monitor
- CVE-2025-3354IBM Tivoli Monitoring code execution39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-1183Jul 17, 2017 · IBM Tivoli Monitoring Portal v6 could allow a local (network adjacent) attacker to modify SQL commands to the Portal Server, when default…30Monitor
- ← EarlierCVE-2017-1635Dec 13, 2017 · IBM Tivoli Monitoring V6 6.2.2.x could allow a remote attacker to execute arbitrary code on the system, caused by a use-after-free error.33Monitor
- Later →CVE-2017-1794Sep 19, 2018 · 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…30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.