LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4529: IBM Maximo Asset Management 7.6.0 and 7.6.1 is vulnerable to server side request forgery (SSRF).

IBM Maximo Asset Management 7.6.0 and 7.6.1 is vulnerable to server side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks. IBM X-Force ID: 182713.

HighCVSS 7.3Not KEV-listedUpdated
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 an SSRF flaw that can make the server send unauthorized requests. For executives, the concern is internal visibility: a compromised or misused Maximo path could help map internal networks or support follow-on attacks.

Executive priority

Prioritize remediation for any affected Maximo instance with broad user access or internal network reach. The issue can convert application access into internal network reconnaissance capability, which raises business risk beyond the Maximo application itself.

Technical view

CVE-2020-4529 is an SSRF in IBM Maximo Asset Management 7.6.0 and 7.6.1. IBM describes an authenticated attacker sending unauthorized requests from the system, potentially enabling network enumeration or other attacks. The provided CVSS 3.0 score is 7.3 high, with network attack vector and low complexity.

Likely exposure

Exposure is limited to organizations running IBM Maximo Asset Management 7.6.0 or 7.6.1. Risk is higher where Maximo is reachable by many users or where the application server has broad outbound access to internal services.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat this as a serious authenticated SSRF risk, but do not assume known in-the-wild exploitation from the provided evidence.

Researcher notes

Evidence is concise and vendor-centered. The description says authenticated attacker, while the provided CVSS vector lists PR:N, so validation should rely on IBM guidance for exact preconditions. No CWE, exploit detail, or specific fix version is provided in the bundle.

Mitigation direction

  • Identify all Maximo Asset Management 7.6.0 and 7.6.1 deployments.
  • Review IBM advisory and X-Force entry for vendor-supported remediation.
  • Limit Maximo server outbound access to required internal and external destinations.
  • Restrict Maximo access to trusted users and networks where operationally possible.
  • Monitor for unusual outbound requests from Maximo application servers.

Validation and detection

  • Confirm deployed Maximo versions against the affected 7.6.0 and 7.6.1 range.
  • Check whether IBM-recommended remediation is applied on each affected instance.
  • Review proxy, firewall, and application logs for unexpected server-originated requests.
  • Verify Maximo servers cannot reach sensitive internal metadata or admin endpoints.
  • Document exposed instances, owners, remediation status, and compensating controls.
Prepared
Confidence
medium
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

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material 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-2020-4529 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.3 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/UI:N/S:U/AC:L/C:L/PR:N/AV:N/A:L/I:L/RC:C/E:U/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.3CVSS 3.0HighCVSS:3.0/UI:N/S:U/AC:L/C:L/PR:N/AV:N/A:L/I:L/RC:C/E:U/RL:O3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

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

Vector: CVSS:3.0/UI:N/S:U/AC:L/C:L/PR:N/AV:N/A:L/I:L/RC:C/E:U/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.