LiveActive security incident?Get immediate response
CVE Record

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 priv...

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-1794 affects IBM Tivoli Monitoring and could let a low-privileged TEPS user gain higher privileges or trigger service disruption through uncontrolled memory growth. It is rated high severity, but the provided evidence says exploitation requires high complexity.

Executive priority

Prioritize remediation where IBM Tivoli Monitoring supports critical operations or is reachable by broad internal user groups. The issue can affect both privilege boundaries and availability, but evidence does not show active exploitation in the supplied sources.

Technical view

IBM Tivoli Monitoring 6.2.3 through 6.2.3.5 and 6.3.0 through 6.3.0.7 have TEPS privilege escalation and possible denial-of-service risk. CVSS v3.0 score is 7.5 with network attack vector, low privileges required, no user interaction, high complexity, and high confidentiality, integrity, and availability impact.

Likely exposure

Organizations running affected IBM Tivoli Monitoring TEPS versions are the likely exposure. Risk is higher where TEPS is network-reachable by non-administrative users. The source bundle does not identify specific deployment configurations beyond product and version ranges.

Exploitation context

The source bundle does not report active exploitation. KEV status is false, and the CVSS exploit maturity value is unproven. Treat this as a serious authenticated exposure, not as confirmed in-the-wild exploitation.

Researcher notes

Evidence is limited to CVE metadata, IBM X-Force reference, and IBM support reference. No CWE, exploit details, or exact fixed build are included in the source bundle. Avoid assuming affected components beyond TEPS and listed IBM Tivoli Monitoring versions.

Mitigation direction

  • Inventory IBM Tivoli Monitoring versions and identify TEPS components.
  • Review IBM advisory swg22014097 for official remediation guidance.
  • Prioritize upgrade or vendor-directed remediation for affected versions.
  • Restrict TEPS network access to trusted administrative paths.
  • Monitor TEPS resource growth and service availability until remediated.

Validation and detection

  • Confirm deployed IBM Tivoli Monitoring version against listed affected versions.
  • Verify whether TEPS is enabled and reachable over the network.
  • Review user roles with TEPS access, especially low-privileged accounts.
  • Check IBM advisory status for the exact fixed or remediated release.
  • Review monitoring logs for unusual TEPS memory growth or privilege changes.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-1794 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.0HighCVSS:3.0/A:H/AC:H/AV:N/C:H/I:H/PR:L/S:U/UI:N/E:U/RC:C/RL:O1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.5High
CVSS 3.0 vector shape for CVE-2017-1794Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMTivoli Monitoring6.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.7Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.