CVE-2020-8482
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsecure 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceABB Device Library Wizard versions 6.0.X, 6.0.3.1, and 6.0.3.2 store sensitive information insecurely, allowing an unauthenticated low-privilege user to read files containing confidential data. The vulnerability stems from inadequate access controls or lack of encryption on stored sensitive files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 6.0.0, <= 6.0.3.2= 6.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify ABB Device Library Wizard installationCheck for the presence of ABB Device Library Wizard on the system. Look for the application in standard program installation directories or check for related processes/services.Affected if The application is installed on the system.
-
Determine the installed versionOpen the application or check itsAbout/Version information panel to find the exact version number of ABB Device Library Wizard.Affected if The installed version is 6.0.0 through 6.0.3.2 inclusive, or exactly version 6.1.0.
-
Locate application data directoriesIdentify where ABB Device Library Wizard stores its configuration and data files. Common locations include user profile folders, program data directories, or application-specific data folders.Affected if The application stores data in directories accessible to low-privilege users.
-
Inspect sensitive file permissionsExamine the access control permissions on directories and files where the application stores confidential data. Verify which user accounts can read these files.Affected if Files containing confidential data are readable by unauthenticated or low-privilege users without proper authentication.
-
Check for unencrypted sensitive filesExamine stored configuration files, credentials, or data files to determine if sensitive information is stored in plaintext or without encryption.Affected if Sensitive data is stored in an unencrypted or weakly protected format.
A user is affected if ABB Device Library Wizard version 6.0.0-6.0.3.2 or 6.1.0 is installed and stores sensitive files with inadequate access controls or without encryption, allowing unauthorized file access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper file access controls and encrypt sensitive data at rest to ensure only authorized users can access confidential information.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8482 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-8482 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data