LiveActive security incident?Get immediate response
CVE Record

CVE-2019-4066: IBM Intelligent Operations Center (IOC) 5.1.0 through 5.2.0 could allow an authenciated user to create arbi...

IBM Intelligent Operations Center (IOC) 5.1.0 through 5.2.0 could allow an authenciated user to create arbitrary users which could cause ID management issues and result in code execution. IBM X-Force ID: 157011.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2019-4066 affects IBM Intelligent Operations Center 5.1.0 through 5.2.0. An authenticated user could create arbitrary users, disrupting identity management and potentially leading to code execution. The issue is high severity because it is network-accessible, low-complexity, and requires only low privileges, but the provided sources do not show active exploitation.

Executive priority

Prioritize remediation for any internet- or broadly network-accessible IOC deployment. This is not confirmed exploited in the provided sources, but the impact can include identity compromise and code execution, making delay risky for affected systems.

Technical view

The CVSS 3.0 vector reports network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact. IBM X-Force tracks it as ID 157011. Exploit maturity is listed as unproven, and remediation level indicates an official fix exists.

Likely exposure

Exposure is limited to IBM Intelligent Operations Center deployments running affected 5.1.0, 5.1.0.1 through 5.1.0.14, or 5.2.0 versions where authenticated users can access the vulnerable product.

Exploitation context

The provided bundle does not identify public exploitation or CISA KEV listing. The CVSS metadata says exploitation is unproven. The risk remains material because abuse requires only authenticated network access with low privileges and could affect identity management and code execution outcomes.

Researcher notes

Evidence is concise and vendor-centered. No CWE is supplied. The key validation questions are version exposure, authenticated access paths, account creation audit trails, and whether IBM’s official remediation has been applied. Avoid assuming exploit availability beyond the unproven exploit maturity value.

Mitigation direction

  • Check IBM advisory ibm10879381 for the official remediation.
  • Apply IBM’s official fix or upgrade path for affected IOC versions.
  • Restrict IOC access to trusted authenticated users until remediated.
  • Review IOC identity management logs for unexpected user creation.
  • Remove unauthorized accounts found during the exposure window.

Validation and detection

  • Inventory IBM Intelligent Operations Center versions in production and staging.
  • Confirm whether versions match 5.1.0 through 5.2.0 affected releases.
  • Verify installed fix level against IBM advisory ibm10879381.
  • Review user account creation history for unexplained accounts.
  • Check administrative and identity-management logs for suspicious changes.
Prepared
Confidence
high
Sources
4

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-2019-4066 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
8.8 (3.0)
Known Exploited
No
Published

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

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

Vulnerability scoring details

Base CVSS 3.0 score

8.8High
CVSS 3.0 vector shape for CVE-2019-4066Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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.