# CVE-2020-8482: ABB Device Library Wizard Information Disclosure Vulnerability

> Unauthenticated low-privilege users can read files containing confidential data due to insecure storage in ABB Device Library Wizard.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f8fq-6xp7-8xvq

## What is CVE-2020-8482?

CVE-2020-8482 is a high-severity vulnerability in ABB Device Library Wizard, published on 29 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insecure storage of sensitive information in ABB Device Library Wizard versions 6.0.X, 6.0.3.1 and 6.0.3.2 allows unauthenticated low privilege user to read file that contains confidential data

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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

It affects 1 product.


Products: Abb Device Library Wizard.

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

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

## Is CVE-2020-8482 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8482 is a high-severity vulnerability in ABB Device Library Wizard, published on 29 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8482 in the wild and no public exploit code.

Affected product: ABB Device Library Wizard. 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-8482/ (Markdown: https://insights.sbomify.com/CVE-2020-8482/index.md)
```

## Sources

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

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