# CVE-2020-12038: Memory corruption in EDS Subsystem, FactoryTalk Linx software (Previously called RSLinx Enterprise), RSLinx Classic, RSNetWorx software, Studio 5000 Logix Designer software

> Attackers can cause denial of service in Rockwell Automation industrial software by crafting malicious EDS files that trigger memory corruption.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gxv4-cqjv-gg3m

## What is CVE-2020-12038?

CVE-2020-12038 is a medium-severity memory corruption vulnerability in EDS Subsystem, FactoryTalk Linx software (Previously called RSLinx Enterprise), RSLinx Classic, RSNetWorx software, Studio 5000 Logix Designer software, published on 19 May 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Products that use EDS Subsystem: Version 28.0.1 and prior (FactoryTalk Linx software (Previously called RSLinx Enterprise): Versions 6.00, 6.10, and 6.11, RSLinx Classic: Version 4.11.00 and prior, RSNetWorx software: Version 28.00.00 and prior, Studio 5000 Logix Designer software: Version 32 and prior) is vulnerable. A memory corruption vulnerability exists in the algorithm that matches square brackets in the EDS subsystem. This may allow an attacker to craft specialized EDS files to crash the EDSParser COM object, leading to denial-of-service conditions.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 5 products.


Products: Rockwellautomation Eds Subsystem, Rockwellautomation Rslinx, Rockwellautomation Rslinx Enterprise, Rockwellautomation Rsnetworx, Rockwellautomation Studio 5000 Logix Designer.

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

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

## Is CVE-2020-12038 being exploited?

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

## Other vulnerabilities in EDS Subsystem, FactoryTalk Linx software (Previously called RSLinx Enterprise), RSLinx Classic, RSNetWorx software, Studio 5000 Logix Designer software

- [CVE-2020-12034](https://insights.sbomify.com/CVE-2020-12034/): SQL injection in EDS Subsystem, FactoryTalk Linx software (Previously called RSLinx Enterprise), RSLinx Classic, RSNetWorx software, Studio 5000 Logix Designer software (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12038 is a medium-severity memory corruption vulnerability in EDS Subsystem, FactoryTalk Linx software (Previously called RSLinx Enterprise), RSLinx Classic, RSNetWorx software, Studio 5000 Logix Designer software, published on 19 May 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-12038 in the wild and no public exploit code.

Affected product: EDS Subsystem, FactoryTalk Linx software (Previously called RSLinx Enterprise), RSLinx Classic, RSNetWorx software, Studio 5000 Logix Designer software. 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-12038/ (Markdown: https://insights.sbomify.com/CVE-2020-12038/index.md)
```

## Sources

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

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