CVE-2020-11642
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 · uneditedThe local file inclusion vulnerability present in B&R SiteManager versions <9.2.620236042 allows authenticated users to impact availability of SiteManager instances.
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 confidenceLocal file inclusion vulnerability in B&R SiteManager versions prior to 9.2.620236042 allows authenticated users to access arbitrary local files on the system, potentially leading to information disclosure and availability impacts through denial of service conditions.
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< 9.2.620236042CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 B&R SiteManager installationCheck for the presence of B&R SiteManager on the system. Common installation paths may include C:\Program Files\B&R Automation\SiteManager or /opt/br/sitemanager. Look for executable files named sitemanager.exe, sitemanager, or related service processes.Affected if B&R SiteManager software is installed on the system
-
Determine installed SiteManager versionLocate the version information for the installed SiteManager. This is typically available in the software itself (about dialog), in installed program files, or via the web interface if accessible. Check executable file properties or consult product documentation for version lookup methods.Affected if The installed version cannot be determined or is below 9.2.620236042
-
Compare version against affected rangeCompare the identified version number to the vulnerable range: versions prior to 9.2.620236042. Note that version numbers follow the format 9.2.620236042.Affected if The installed version is lower than 9.2.620236042 (for example, 9.2.5 or any 9.x version prior to the patched release)
-
Verify authentication configurationSince the vulnerability requires authenticated access, check whether user authentication is enabled on the SiteManager. Review authentication settings in the SiteManager configuration, user management, or access control settings.Affected if Authentication is enabled and users with local access exist on the system
A system is affected if B&R SiteManager is installed and the running version is lower than 9.2.620236042, with authentication enabled to allow exploitation.
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 data9.2.620236042
Upgrade B&R SiteManager to version 9.2.620236042 or later to remediate this vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11642 — 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-11642 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