LiveActive security incident?Get immediate response
CVE Record

CVE-2022-42442: IBM Robotic Process Automation for Cloud Pak information disclosure

IBM Robotic Process Automation for Cloud Pak 21.0.1, 21.0.2, 21.0.3, 21.0.4, and 21.0.5 is vulnerable to exposure of the first tenant owner e-mail address to users with access to the container platform. IBM X-Force ID: 238214.

LowCVSS 3.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a limited information disclosure in IBM Robotic Process Automation for Cloud Pak. Users who already have access to the container platform may see the first tenant owner email address. The disclosed data is low sensitivity, but it can support targeting, social engineering, or account reconnaissance.

Executive priority

Handle through normal vulnerability management, not emergency response. Prioritize if the tenant owner account is privileged, public-facing, or frequently targeted by phishing.

Technical view

CVE-2022-42442 is CWE-200 affecting IBM Robotic Process Automation for Cloud Pak 21.0.1 through 21.0.5. CVSS 3.1 is 3.3: local access, low complexity, low privileges, no user interaction, confidentiality impact only. Integrity and availability are not impacted in the provided sources.

Likely exposure

Exposure is limited to organizations running the listed IBM RPA for Cloud Pak versions and granting users access to the underlying container platform. The source bundle does not identify broader remote exposure.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not state active exploitation. Practical misuse appears limited to authorized or low-privileged platform users learning a tenant owner email address.

Researcher notes

Evidence supports a narrow confidentiality issue only. The provided data does not name exploit activity, public exploit code, or a specific patch level. Keep affected-version conclusions constrained to 21.0.1 through 21.0.5.

Mitigation direction

  • Review IBM’s advisory for fixed versions or vendor-approved remediation guidance.
  • Limit container platform access to users with a clear operational need.
  • Treat the first tenant owner email address as potentially disclosed.
  • Strengthen phishing monitoring and account protections for the affected owner account.

Validation and detection

  • Inventory IBM RPA for Cloud Pak deployments and version numbers.
  • Confirm whether versions 21.0.1 through 21.0.5 are present.
  • Review which users or groups have container platform access.
  • Check platform-visible metadata for exposure of the first tenant owner email address.
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.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique 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-42442 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
Low
CVSS
3.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

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
3.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N1.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.3Low
CVSS 3.1 vector shape for CVE-2022-42442Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

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
IBMRobotic Process Automation for Cloud Pak21.0.1, 21.0.2, 21.0.3, 21.0.4, 21.0.5unaffected
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.