dbcve.org
Arcsight LoggerApplication · Microfocus

CVE-2022-26331

MEDIUM · 6.1 CVSS v3.1 Published 2022-08-31
Fix available
A fix is available. Upgrade to 7.2.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Potential vulnerabilities have been identified in Micro Focus ArcSight Logger. The vulnerabilities could be remotely exploited resulting in Information Disclosure, or Self Cross-Site Scripting (XSS). This issue affects: Micro Focus ArcSight Logger versions prior to v7.2.2 version and prior versions.

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 confidence

Multiple vulnerabilities in Micro Focus ArcSight Logger allow remote exploitation leading to Information Disclosure or Self Cross-Site Scripting (XSS). Self XSS typically requires tricking a user into executing malicious scripts in their own browser context, while Information Disclosure could expose sensitive data. The CVSS 6.1 suggests limited scope impact with user interaction potentially required.

MitigationUpgrade Micro Focus ArcSight Logger to version 7.2.2 or later to address these vulnerabilities. Until upgrade is possible, restrict access to the Logger web interface and monitor for suspicious user activity.

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
Arcsight LoggerApplication
Affected:< 7.2.2

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ArcSight Logger is installed
    Check for ArcSight Logger installation directories, services, or running processes. Common locations include /opt/arcsight/logger or C:\arcsight\logger. On Linux, run 'ps aux | grep arcsight' or 'systemctl list-units | grep logger'. On Windows, check Services for 'ArcSight Logger'.
    Affected if ArcSight Logger is present on the system and the version is below 7.2.2
  2. Determine installed ArcSight Logger version
    Check the version file or use the management interface. Common locations: /opt/arcsight/logger/current/arcsight/logger/version.properties or inspect the logger About page via the web UI at https://<hostname>:443/logger. Alternatively, check the installer package or RPM/DEB package version with 'rpm -qi arcsight-logger' or 'dpkg -l arcsight-logger'.
    Affected if The installed version is any version prior to 7.2.2 (for example, 7.1.x, 7.0.x, 6.x)
  3. Verify if web interface is accessible
    Attempt to access the Logger web UI. Check if port 443 or 8443 is listening with 'netstat -tlnp | grep -E "(443|8443)"' or test connectivity with 'curl -kI https://<loggerhost>:443/logger'. Review network configuration to confirm the web interface is exposed externally or to untrusted networks.
    Affected if The ArcSight Logger web interface is accessible over the network and the installed version is below 7.2.2
  4. Check for suspicious user activity or indicators of compromise
    Review ArcSight Logger audit logs and access logs for unusual patterns. Look for: (1) Unexpected requests to endpoints that could leak information, (2) Scripts or HTML in search fields or user inputs, (3) Unusual data exports or queries. Logs are typically in /opt/arcsight/logger/logs/ or accessible via the UI.
    Affected if Exploitation indicators are found in logs and the version is below 7.2.2

A user is affected if Micro Focus ArcSight Logger is installed with any version lower than 7.2.2 and the web interface is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.2.2 or later
Fixed in 7.2.2
Interim mitigation

Upgrade Micro Focus ArcSight Logger to version 7.2.2 or later to address these vulnerabilities. Until upgrade is possible, restrict access to the Logger web interface and monitor for suspicious user activity.

Recommended fix High confidence

ArcSight Logger 7.2.2 or later

  1. 1. Identify current ArcSight Logger version by accessing the Logger web interface or checking system information
  2. 2. Review upgrade prerequisites and compatibility documentation in the Micro Focus ArcSight Logger documentation portal
  3. 3. Create a complete backup of the current Logger configuration and database
  4. 4. Schedule a maintenance window for the upgrade process
  5. 5. Download ArcSight Logger version 7.2.2 or later from the Micro Focus support portal
  6. 6. Execute the upgrade following the official upgrade guide for your deployment type (standalone or distributed)
  7. 7. After upgrade completes, verify the Logger services are running properly
  8. 8. Confirm the version has been updated to 7.2.2 or later in the web interface

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Arcsight Logger Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26331 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26331 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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