LiveActive security incident?Get immediate response
CVE Record

CVE-2022-22416: IBM Sterling Partner Engagement Manager 6.1.2, 6.2, and Cloud/SasS 22.2 is vulnerable to server-side reques...

IBM Sterling Partner Engagement Manager 6.1.2, 6.2, and Cloud/SasS 22.2 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: 223126.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue lets a logged-in user make IBM Sterling Partner Engagement Manager send unauthorized requests from the PEM system. The main business risk is using that trusted server as a vantage point to map internal network services or support follow-on attacks. It is not listed as known exploited in CISA KEV.

Executive priority

Treat as a normal-priority medium vulnerability, accelerated where PEM is internet-facing or exposed to many partner users. The issue is credible but not currently KEV-listed as exploited.

Technical view

CVE-2022-22416 is an SSRF vulnerability in IBM Sterling Partner Engagement Manager 6.1.2, 6.2, and Cloud/SaaS 22.2. CVSS 3.0 score is 5.4, with network access, low privileges, no user interaction, low confidentiality and integrity impact, and no availability impact.

Likely exposure

Exposure is limited to organizations running the named IBM Sterling Partner Engagement Manager versions, especially where authenticated partner or user access is broad or externally reachable.

Exploitation context

The provided sources do not show active exploitation or public weaponization. The CVSS vector indicates an authenticated attacker is required. Impact is primarily internal request origination, network enumeration, and possible support for other attacks.

Researcher notes

The source bundle identifies SSRF behavior and affected versions but does not include endpoint details, proofs of concept, or specific fixed build numbers. Avoid assuming exploitability beyond authenticated unauthorized request origination.

Mitigation direction

  • Review IBM advisory 6604989 and apply IBM-recommended fixes or service updates.
  • Confirm IBM Cloud/SaaS remediation status with IBM support for hosted 22.2 environments.
  • Restrict PEM access to trusted authenticated users and partner accounts.
  • Limit outbound network reachability from PEM systems where operationally feasible.
  • Monitor PEM-originated outbound requests for unusual destinations or patterns.

Validation and detection

  • Inventory IBM Sterling Partner Engagement Manager deployments and versions.
  • Confirm whether versions 6.1.2, 6.2, or Cloud/SaaS 22.2 are present.
  • Check patch or service update status against IBM advisory 6604989.
  • Review access controls for authenticated PEM users and partner accounts.
  • Review network logs for unexpected PEM-originated internal or external requests.
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-2022-22416 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.4 (3.0)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.0 score

5.4Medium
CVSS 3.0 vector shape for CVE-2022-22416Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/UI:N/AV:N/PR:L/C:L/S:U/A:N/I:L/AC: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
IBMSterling Partner Engagement Manager on Cloud22.2Listed
IBMSterling Partner Engagement Manager6.1.2, 6.2Listed
Weakness

CWE details

No CWE listed

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