CVE-2023-0580
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 vulnerability in ABB My Control System (on-premise) allows an attacker who successfully exploited this vulnerability to gain access to the secure application data or take control of the application. Of the services that make up the My Control System (on-premise) application, the following ones are affected by this vulnerability: User Interface System Monitoring1 Asset Inventory This issue affects My Control System (on-premise): from 5.0;0 through 5.13.
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 confidenceThis vulnerability involves the storage of sensitive data (possibly credentials, keys, or application secrets) in an unencrypted or inadequately protected manner within the ABB My Control System on-premise application. An attacker with access to the system storage or database could read this sensitive data in plaintext, enabling unauthorized access to the application or its secure functions.
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>= 5.0, <= 5.13CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify the installed ABB My Control System versionCheck the application version through its built-in about section, installer properties, or version file in the installation directory. Common locations include the main executable's properties, a version.info file, or the application's help/about dialog.Affected if The version number is 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 5.9, 5.10, 5.11, 5.12, or 5.13 (any version from 5.0 through 5.13 inclusive).
-
Locate the application data storage directoryIdentify where ABB My Control System stores its configuration and data files. Common locations include installation folders, ProgramData directories, or application-specific data folders. Check the application's documentation or configuration for storage paths.Affected if The application stores data in a location accessible to the account running the vulnerability assessment.
-
Examine configuration files for plaintext sensitive dataReview configuration files (such as XML, JSON, INI, or config files) in the application data directory for credentials, API keys, passwords, or other secrets. Look for fields containing values that appear to be passwords, keys, or authentication tokens stored without encryption indicators.Affected if Credentials, API keys, passwords, or application secrets are found stored in plaintext or weakly obfuscated format within configuration files.
-
Inspect the application database for unencrypted sensitive fieldsIf the application uses a database (such as SQLite, SQL Server, or MySQL), examine the database tables for columns containing sensitive data. Check whether sensitive fields like passwords, keys, or secrets are stored as plaintext rather than using cryptographic hashing or encryption.Affected if The database contains plaintext sensitive data (credentials, keys, secrets) in readable form rather than hashed or encrypted.
-
Verify file system permissions on sensitive storage locationsCheck that only authorized system or application accounts have read access to the directories and files containing sensitive configuration and data. Verify that low-privilege users or anonymous accounts cannot read these files.Affected if Sensitive configuration or data files are readable by unauthorized users or groups beyond the application service account.
A user is affected if they are running ABB My Control System version 5.0 through 5.13 AND have sensitive data (credentials, keys, or secrets) stored in plaintext within the application's configuration files or database.
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 dataUpgrade to ABB My Control System version 5.14 or later which contains the security fix. If patching is not immediately possible, implement compensating controls such as restricting system access, encrypting the underlying storage/disk, and auditing access to sensitive files.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0580 — 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-2023-0580 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