CVE-2020-11851
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 · uneditedArbitrary code execution vulnerability on Micro Focus ArcSight Logger product, affecting all version prior to 7.1.1. The vulnerability could be remotely exploited resulting in the execution of arbitrary code.
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 confidenceMicro Focus ArcSight Logger contains an arbitrary code execution vulnerability that can be exploited remotely without authentication, allowing an attacker to execute arbitrary code on the affected system. The vulnerability affects all versions prior to 7.1.1.
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< 7.1.1CVSS 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.
-
Verify ArcSight Logger installationCheck for the presence of Micro Focus ArcSight Logger by looking for its installation directory (typically under /opt/arcsight/logger or C:\arcsight\logger on Windows) or by searching for the arcsight logger service process.Affected if ArcSight Logger is installed on the system.
-
Determine installed Logger versionLocate the version file or use the product's command-line interface. Common locations include a version.info file in the installation root, or run: ./arcsight logger version (Linux) or the equivalent Windows command.Affected if The version cannot be determined or the installed version is below 7.1.1.
-
Compare version against the affected rangeTake the installed version number and compare it numerically to 7.1.1. All versions before 7.1.1 (including 7.0.x, 6.x, and earlier) are affected.Affected if The installed version is less than 7.1.1 (e.g., 7.0.0, 6.11.2, etc.).
-
Confirm Logger service is runningCheck if the ArcSight Logger service is active. On Linux, use: ps aux | grep arcsight or systemctl status arcsight-logger. On Windows, check the Windows Services console for 'Arcsight Logger' service.Affected if The Logger service is running and version is below 7.1.1.
-
Assess network exposureReview firewall rules and network configuration to determine if Logger management or web interfaces are accessible from untrusted networks. Check listening ports (typically 443, 8443 for web interfaces).Affected if Logger interfaces are exposed to untrusted networks and the version is below 7.1.1.
The environment is affected if Micro Focus ArcSight Logger is installed, the service is running, and the installed version is below 7.1.1.
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.
dbcve · scoped7.1.1
Upgrade Micro Focus ArcSight Logger to version 7.1.1 or later to remediate this vulnerability. If immediate upgrading is not possible, restrict network access to the Logger interfaces and implement additional network segmentation as a temporary compensating control.
7.1.1
- Obtain ArcSight Logger version 7.1.1 or later from the Micro Focus official software distribution portal
- Review the ArcSight Logger upgrade guide and release notes for version 7.1.1
- Create a complete backup of the current Logger configuration and data
- Schedule a maintenance window to minimize business impact
- Stop the ArcSight Logger services before starting the upgrade
- Run the installer or follow the documented upgrade procedure for version 7.1.1
- After upgrade completion, verify the installed version shows 7.1.1 or later
- Start the Logger services and confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11851 — 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-11851 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