CVE-2020-11644
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 information disclosure vulnerability present in B&R GateManager 4260 and 9250 versions <9.0.20262 and GateManager 8250 versions <9.2.620236042 allows authenticated users to generate fake audit log messages.
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 · high confidenceB&R GateManager versions prior to 9.0.20262 (models 4260/9250) and prior to 9.2.620236042 (model 8250) contain an information disclosure vulnerability where authenticated users can generate fake audit log messages. This compromises audit log integrity, allowing attackers to hide malicious activity or impede forensic investigations by injecting false records.
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.0.20262< 9.0.20262< 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Identify the GateManager model numberAccess the GateManager web interface or system information page to determine the model (4260, 9250, or 8250). This is typically visible in the device status or system information section of the administrative console.Affected if The model is 4260, 9250, or 8250, as these are the affected models.
-
Determine the installed firmware versionLocate the firmware version in the GateManager administrative interface, typically found under System Info, Status, or About sections. Alternatively, check the boot log or system banner displayed upon login.Affected if The exact version string cannot be determined from the provided information; you must obtain the precise version number to proceed.
-
Compare firmware version against affected rangesCompare your installed version to the following thresholds: for models 4260 and 9250, any version below 9.0.20262 is affected; for model 8250, any version below 9.2.620236042 is affected.Affected if For models 4260/9250: version is below 9.0.20262. For model 8250: version is below 9.2.620236042.
-
Verify if user authentication is enabledCheck the GateManager user authentication settings in the administrative console. Confirm whether local user accounts, LDAP integration, or other authentication methods are configured and active.Affected if User authentication is enabled, as the vulnerability requires authenticated users to inject fake audit log entries.
-
Inspect audit log access controlsReview the audit log configuration to determine if standard authenticated users have the ability to generate or modify audit log entries. Check user role permissions related to logging functions.Affected if Authenticated users with standard or elevated privileges can generate audit log messages, enabling the exploitation of this vulnerability.
You are affected if your GateManager model is 4260 or 9250 with firmware below 9.0.20262, or model 8250 with firmware below 9.2.620236042, and user authentication is enabled allowing logged users to interact with audit log functionality.
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.0.202629.2.620236042
Upgrade GateManager firmware to version 9.0.20262 or higher (4260/9250) or 9.2.620236042 or higher (8250). Review existing audit logs for suspicious entries that may indicate exploitation.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11644 — 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-11644 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