CVE-2020-11639
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 · uneditedAn attacker could exploit the vulnerability by injecting garbage data or specially crafted data. Depending on the data injected each process might be affected differently. The process could crash or cause communication issues on the affected node, effectively causing a denial-of-service attack. The attacker could tamper with the data transmitted, causing the product to store wrong information or act on wrong data or display wrong information. This issue affects Advant MOD 300 AdvaBuild: from 3.0 through 3.7 SP2. For an attack to be successful, the attacker must have local access to a node in the system and be able to start a specially crafted application that disrupts the communication. An attacker who successfully exploited the vulnerability would be able to manipulate the data in such way as allowing reads and writes to the controllers or cause Windows processes in 800xA for MOD 300 and AdvaBuild to crash.
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 is a local privilege vulnerability in Advant MOD 300 AdvaBuild (versions 3.0-3.7 SP2) where an attacker with local node access can inject specially crafted data into the system. The vulnerability allows process crashes causing denial-of-service and enables data manipulation leading to unauthorized read/write access to controllers or Windows process crashes in 800xA for MOD 300 and AdvaBuild.
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>= 3.0, < 3.7= 3.7CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify Advabuild installation existsCheck for Advabuild in the list of installed programs via Windows Control Panel Programs and Features, or look for the Advabuild installation directory (typically under C:\Program Files\ABB\Advabuild or similar locations)Affected if Advabuild is present on the system
-
Determine installed Advabuild versionRight-click the main Advabuild executable (such as Advabuild.exe) and select Properties, then view the Details tab to find the File Version. Alternatively, check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an Advabuild entry and read the DisplayVersion valueAffected if The displayed version falls within >= 3.0 and <= 3.7 (including version 3.7)
-
Confirm affected version rangeCompare the identified version number against the vulnerable range: versions 3.0 through 3.7 SP2 are affected. Versions below 3.0 or above 3.7 SP2 (with patch applied) are not vulnerableAffected if Installed version is 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, or any 3.7 SP1/SP2 variant prior to patch
If Advabuild is installed and the version is 3.0 through 3.7 (including 3.7 SP2) without the vendor patch applied, the system is affected by this vulnerability.
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 data3.7
Apply available vendor patches for AdvaBuild 3.7 SP2 or later; restrict local access to system nodes and monitor for specially crafted applications.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.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 $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11639 — 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-11639 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