LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4311: IBM Tivoli Monitoring 6.3.0 could allow a local attacker to execute arbitrary code on the system.

IBM Tivoli Monitoring 6.3.0 could allow a local attacker to execute arbitrary code on the system. By placing a specially crafted file, an attacker could exploit this vulnerability to load other DLL files located in the same directory and execute arbitrary code on the system. IBM X-Force ID: 177083.

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

Security readout for executives and security teams

Plain-English summary

CVE-2020-4311 affects IBM Tivoli Monitoring 6.3.0. A local attacker could place a crafted file so the application loads DLL files from the same directory, allowing arbitrary code execution. Impact is serious because code execution can compromise confidentiality, integrity, and availability on affected hosts.

Executive priority

Treat this as high priority where Tivoli Monitoring 6.3.0 exists on important systems. The issue is local, not remotely exploitable from the cited data, but successful exploitation could give an attacker code execution on monitoring infrastructure.

Technical view

The source data describes a local arbitrary code execution issue in IBM Tivoli Monitoring 6.3.0 involving DLL loading from the same directory as a specially crafted file. CVSS v3.0 is 7.4 high, with local attack vector, high attack complexity, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to systems running IBM Tivoli Monitoring 6.3.0 where an attacker can place files locally in a relevant directory. The provided sources do not identify other affected versions, components, or platforms.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and the CVSS vector marks exploit maturity as unproven. No cited source in the bundle supports active exploitation. The attack requires local file placement and high complexity.

Researcher notes

The sources provide high-level behavior but no CWE, fixed build detail, or component-level path. Validate exposure through version inventory and directory permission review. Do not assume broader IBM Tivoli versions are affected without vendor evidence.

Mitigation direction

  • Identify all IBM Tivoli Monitoring 6.3.0 installations.
  • Review IBM advisory guidance and apply the vendor-provided official remediation.
  • Restrict local write access to Tivoli Monitoring application directories.
  • Prioritize remediation on shared, administrative, or critical monitoring hosts.

Validation and detection

  • Confirm installed IBM Tivoli Monitoring versions from asset inventory.
  • Check whether affected hosts match IBM Tivoli Monitoring 6.3.0.
  • Review write permissions on relevant application directories.
  • Verify remediation status against IBM advisory or X-Force records.
Prepared
Confidence
high
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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-2020-4311 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.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/S:U/UI:N/A:H/C:H/I:H/PR:N/AC:H/E:U/RL:O/RC:C

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.4CVSS 3.0HighCVSS:3.0/AV:L/S:U/UI:N/A:H/C:H/I:H/PR:N/AC:H/E:U/RL:O/RC:C1.45.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.4High
CVSS 3.0 vector shape for CVE-2020-4311Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/S:U/UI:N/A:H/C:H/I:H/PR:N/AC:H/E:U/RL:O/RC:C

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.3.0Listed
Weakness

CWE details

No CWE listed

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