# CVE-2020-4635: Information disclosure in Resilient

> Attackers can enumerate usernames in IBM Resilient SOAR, leading to sensitive information disclosure.

- **Severity:** Low 3.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w677-6mv7-8r5w

## What is CVE-2020-4635?

CVE-2020-4635 is a low-severity vulnerability in IBM Resilient, published on 19 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Resilient SOAR 40 and earlier could disclose sensitive information by allowing a user to enumerate usernames.

## Which versions are affected by CVE-2020-4635?

It affects 1 product.


Products: Ibm Soar.

## How do I fix CVE-2020-4635?

No fix has been published for CVE-2020-4635 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-4635 being exploited?

There is no known exploitation of CVE-2020-4635 in the wild and no public exploit code.

## Other vulnerabilities in IBM Resilient

- [CVE-2024-38319](https://insights.sbomify.com/CVE-2024-38319/): IBM Security SOAR code execution (high 7.5)
- [CVE-2021-29785](https://insights.sbomify.com/CVE-2021-29785/): Information disclosure in Security SOAR (medium 5.9)
- [CVE-2024-45670](https://insights.sbomify.com/CVE-2024-45670/): IBM Security SOAR weak password recovery mechanism (medium 5.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-4635 and fix it if it is affected.

What it is: CVE-2020-4635 is a low-severity vulnerability in IBM Resilient, published on 19 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-4635 in the wild and no public exploit code.

Affected product: IBM Resilient. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-4635/ (Markdown: https://insights.sbomify.com/CVE-2020-4635/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-4635
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-4635
- OSV: https://osv.dev/vulnerability/CVE-2020-4635

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-4635/
Summaries are generated and may contain mistakes; the official description above is the record.