LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4521: IBM Maximo Asset Management 7.6.0 and 7.6.1 could allow a remote authenticated attacker to execute arbitrar...

IBM Maximo Asset Management 7.6.0 and 7.6.1 could allow a remote authenticated attacker to execute arbitrary code on the system, caused by an unsafe deserialization in Java. By sending specially-crafted request, an attacker could exploit this vulnerability to execute arbitrary code on the system. IBM X-Force ID: 182396.

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

Security readout for executives and security teams

Plain-English summary

IBM Maximo Asset Management 7.6.0 and 7.6.1 have a high-severity flaw that can let a logged-in remote attacker run code on the system. The issue is unsafe Java deserialization, which can turn crafted data into server-side execution.

Executive priority

Treat this as a high-priority remediation item for any affected Maximo deployment. Authenticated access is required, but the business impact can include full system compromise if a vulnerable instance is abused.

Technical view

CVE-2020-4521 is a network-reachable, low-complexity, authenticated remote code execution vulnerability in IBM Maximo Asset Management 7.6.0 and 7.6.1. The CVSS 3.0 score is 8.8, with high confidentiality, integrity, and availability impact and no user interaction required.

Likely exposure

Exposure is limited to organizations running IBM Maximo Asset Management 7.6.0 or 7.6.1, especially where authenticated users can reach Maximo over a network.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires authenticated access, but the impact is severe because successful abuse can execute arbitrary code on the system.

Researcher notes

The bundle names unsafe Java deserialization as the root cause and IBM X-Force ID 182396. Patch specifics are not included in the provided text, so fixed versions and interim mitigations should be taken from IBM’s advisory.

Mitigation direction

  • Identify any IBM Maximo Asset Management 7.6.0 or 7.6.1 instances.
  • Review IBM advisory 6332587 for official fix or upgrade guidance.
  • Restrict Maximo access to trusted networks and required users only.
  • Review Maximo user privileges and remove unnecessary authenticated access.
  • Increase monitoring for unusual authenticated activity against Maximo systems.

Validation and detection

  • Inventory Maximo versions and confirm whether 7.6.0 or 7.6.1 is present.
  • Check whether affected Maximo systems are reachable from untrusted networks.
  • Compare installed Maximo levels against IBM’s advisory guidance.
  • Review authentication logs for unusual or unexpected Maximo access patterns.
  • Document remediation status and compensating controls for each instance.
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-4521 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/AC:L/A:H/AV:N/I:H/S:U/C:H/UI:N/PR:L/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
8.8CVSS 3.0HighCVSS:3.0/AC:L/A:H/AV:N/I:H/S:U/C:H/UI:N/PR:L/E:U/RC:C/RL:O2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

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

Vector: CVSS:3.0/AC:L/A:H/AV:N/I:H/S:U/C:H/UI:N/PR:L/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
IBMMaximo Asset Management7.6.0, 7.6.1Listed
Weakness

CWE details

No CWE listed

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