# CVE-2020-14520: The affected product is vulnerable to an information leak, which may allow an attacker to obtain sensitive information on the Ignition 8 (al


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-67jg-mxq3-434p

## What is CVE-2020-14520?

CVE-2020-14520 is a high-severity vulnerability in Ignition 8, published on 31 Jul 2020. 

### Official description

The affected product is vulnerable to an information leak, which may allow an attacker to obtain sensitive information on the Ignition 8 (all versions prior to 8.0.13).

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Inductiveautomation Ignition Gateway.

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

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

## Is CVE-2020-14520 being exploited?

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

## Other vulnerabilities in Ignition 8

- [CVE-2020-10644](https://insights.sbomify.com/CVE-2020-10644/): Deserialization in Ignition 8 Gateway (high 7.5)
- [CVE-2020-12000](https://insights.sbomify.com/CVE-2020-12000/): Deserialization in Ignition 8 Gateway (high 7.5)
- [CVE-2020-12004](https://insights.sbomify.com/CVE-2020-12004/): Missing authorization in Ignition 8 Gateway (high 7.5)
- [CVE-2020-10641](https://insights.sbomify.com/CVE-2020-10641/): Missing authorization in Ignition 8 Gateway (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14520 is a high-severity vulnerability in Ignition 8, published on 31 Jul 2020. 
Exploitation: There is no known exploitation of CVE-2020-14520 in the wild and no public exploit code.

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

## Sources

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

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