Security readout for executives and security teams
Plain-English summary
IBM Resilient SOAR 40 and earlier may let someone discover valid usernames. That is not system compromise by itself, but it can reduce attacker guesswork for phishing, password spraying, or social engineering.
Executive priority
Low urgency unless Resilient SOAR is internet-exposed or tied to sensitive operational workflows. Prioritize routine remediation and reduce external reachability.
Technical view
The CVSS 3.0 vector is 3.7 low: network reachable, no privileges or user interaction, high attack complexity, low confidentiality impact, and no integrity or availability impact. The issue is username enumeration in IBM Resilient SOAR 40 and earlier.
Likely exposure
Exposure is limited to organizations running IBM Resilient SOAR 40 or earlier, especially where the service is reachable by untrusted networks or external users.
Exploitation context
The supplied sources do not state active exploitation. KEV is false, and the CVSS exploit maturity signal is unproven. Treat this as useful reconnaissance rather than direct compromise evidence.
Researcher notes
Evidence is narrow: the bundle identifies username enumeration and CVSS metrics, but not the exact vulnerable endpoint, fixed version, or exploit details. Avoid assuming broader IBM SOAR impact.
Mitigation direction
- Identify any IBM Resilient SOAR 40 or earlier deployments.
- Review IBM advisory 6431265 and X-Force 185502 for vendor remediation.
- Apply IBM-provided fixes or upgrade guidance when confirmed.
- Restrict Resilient SOAR access to trusted networks and users.
- Monitor for repeated account-discovery or failed-authentication patterns.
Validation and detection
- Inventory deployed IBM Resilient SOAR versions and exposure paths.
- Confirm whether affected endpoints are reachable from untrusted networks.
- Use approved, non-invasive checks to assess username disclosure behavior.
- Review logs for unusual repeated username or authentication probes.
- Document compensating controls if vendor remediation is pending.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2020-4635 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/S:U/PR:N/I:N/UI:N/A:N/C:L/AC:H/RL:O/E:U/RC:C
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.0/AV:N/S:U/PR:N/I:N/UI:N/A:N/C:L/AC:H/RL:O/E:U/RC:C2.21.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
3.7LowVector: CVSS:3.0/AV:N/S:U/PR:N/I:N/UI:N/A:N/C:L/AC:H/RL:O/E:U/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/6431265CVE reference · x_refsource_CONFIRM
- ibm-resilient-cve20204635-info-disc (185502)CVE reference · vdb-entry, x_refsource_XF
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.