LiveActive security incident?Get immediate response
CVE Record

CVE-2019-4067: IBM Intelligent Operations Center (IOC) 5.1.0 through 5.2.0 does not require that users should have strong...

IBM Intelligent Operations Center (IOC) 5.1.0 through 5.2.0 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 157012.

MediumCVSS 5.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM Intelligent Operations Center versions 5.1.0 through 5.2.0 did not require strong passwords by default. This raises account compromise risk, especially where exposed accounts use weak or reused passwords. The issue is medium severity because exploitation depends on guessing or obtaining weak credentials, but compromise could expose sensitive IOC data.

Executive priority

Treat this as a targeted hygiene risk, not an emergency. Prioritize remediation if IOC supports operationally sensitive city, infrastructure, or command-center workflows, or if login surfaces are reachable beyond trusted networks.

Technical view

CVE-2019-4067 is an IBM IOC default password-policy weakness affecting 5.1.0, 5.1.0.1 through 5.1.0.14, and 5.2.0. CVSS 3.0 score is 5.9 with network attack vector, no privileges or user interaction required, high attack complexity, and high confidentiality impact.

Likely exposure

Exposure is limited to organizations running IBM Intelligent Operations Center 5.1.0 through 5.2.0, especially deployments reachable over a network and using default or weak password policy settings.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector marks exploit code maturity as unproven. The realistic concern is account compromise through weak passwords rather than a direct software execution flaw.

Researcher notes

Evidence identifies affected versions and weakness type but does not include detailed patch text in the supplied bundle. Avoid assuming exploit availability. Validation should focus on version confirmation, password-policy configuration, and credential-risk review without brute-force testing.

Mitigation direction

  • Identify whether IBM IOC 5.1.0 through 5.2.0 is in use.
  • Review IBM advisory guidance and apply the documented fix or configuration change.
  • Enforce strong password requirements for all IOC user accounts.
  • Reset weak, shared, default, or reused IOC credentials.
  • Add compensating identity controls where supported, such as centralized authentication or MFA.
  • Restrict network access to IOC administrative and user login surfaces.

Validation and detection

  • Inventory IOC instances and record exact installed versions.
  • Review IOC authentication settings for password strength enforcement.
  • Audit user accounts for weak, shared, default, or stale credentials.
  • Check change records against IBM advisory remediation guidance.
  • Confirm exposed login surfaces are limited to intended networks.
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.

cve · low confidence lookup

CVE-2019-4067 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
Medium
CVSS
5.9 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/I:N/AV:N/PR:N/UI:N/AC:H/C:H/S:U/A: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
5.9CVSS 3.0MediumCVSS:3.0/I:N/AV:N/PR:N/UI:N/AC:H/C:H/S:U/A:N/E:U/RC:C/RL:O2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.9Medium
CVSS 3.0 vector shape for CVE-2019-4067Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/I:N/AV:N/PR:N/UI:N/AC:H/C:H/S:U/A: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
IBMIntelligent Operations Center5.1.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1.0.6, 5.1.0.7, 5.1.0.8, 5.1.0.9, 5.1.0.10, 5.1.0.11, 5.1.0.12, 5.1.0.13, 5.1.0.14, 5.2.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.