# CVE-2020-13656: Memory corruption in n/a

> Out-of-bounds read/write in the Hobbes array implementation allows local and remote code execution via RPC.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xv63-73qr-p568

## What is CVE-2020-13656?

CVE-2020-13656 is a critical memory corruption vulnerability in n/a, published on 12 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Morgan Stanley Hobbes through 2020-05-21, the array implementation lacks bounds checking, allowing exploitation of an out-of-bounds (OOB) read/write vulnerability that leads to both local and remote code (via RPC) execution.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Morganstanley Hobbes.

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

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

## Is CVE-2020-13656 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13656 is a critical memory corruption vulnerability in n/a, published on 12 Jun 2020. 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-13656 in the wild and no public exploit code.

Affected product: n/a. 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-13656/ (Markdown: https://insights.sbomify.com/CVE-2020-13656/index.md)
```

## Sources

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

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