# CVE-2020-27283: An attacker could send a specially crafted message to Crimson 3.1 (Build versions prior to 3119.001) that could leak arbitrary memory locations.


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Jan 2021
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-87x6-qp9x-whwg

## What is CVE-2020-27283?

CVE-2020-27283 is a medium-severity vulnerability in Crimson 3.1, published on 6 Jan 2021. 

### Official description

An attacker could send a specially crafted message to Crimson 3.1 (Build versions prior to 3119.001) that could leak arbitrary memory locations.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Redlion Crimson.

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

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

## Is CVE-2020-27283 being exploited?

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

## Other vulnerabilities in Crimson 3.1

- [CVE-2023-5719](https://insights.sbomify.com/CVE-2023-5719/): Red Lion Crimson Improper Neutralization of Null Byte or NUL Character (high 8.8)
- [CVE-2019-10984](https://insights.sbomify.com/CVE-2019-10984/): Memory corruption in Red Lion Controls Crimson (Windows configuration software) (high 7.8)
- [CVE-2019-10996](https://insights.sbomify.com/CVE-2019-10996/): Use after free in Red Lion Controls Crimson (Windows configuration software) (high 7.8)
- [CVE-2022-3090](https://insights.sbomify.com/CVE-2022-3090/): Path traversal in Crimson 3.0 (high 7.5)
- [CVE-2020-27279](https://insights.sbomify.com/CVE-2020-27279/): A NULL pointer deference vulnerability has been identified in the protocol converter. (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-27283 is a medium-severity vulnerability in Crimson 3.1, published on 6 Jan 2021. 
Exploitation: There is no known exploitation of CVE-2020-27283 in the wild and no public exploit code.

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

## Sources

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

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