dbcve.org
Arcsight LoggerApplication · Microfocus

CVE-2022-26330

HIGH · 7.5 CVSS v3.1 Published 2022-08-31
Fix available
A fix is available. Upgrade to 7.2.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · high confidence

Micro Focus ArcSight Logger contains vulnerabilities allowing remote unauthenticated attackers to exploit Information Disclosure or Self Cross-Site Scripting (XSS). The Self XSS vulnerability typically requires the attacker to persuade a user to inject malicious script into input fields, which then executes when the user views the affected content.

MitigationUpgrade Micro Focus ArcSight Logger to version 7.2.2 or later to remediate these vulnerabilities.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the installed ArcSight Logger version
    Access the product's About page, system information panel, or use the product's version lookup command/tool. Common locations include the administration console or help menu.
    Affected if The installed version is any release prior to 7.2.2 (for example, 7.1.x, 7.0.x, or earlier releases).
  2. Confirm the web interface is accessible
    Verify that the ArcSight Logger web interface is reachable over the network. Attempt to access the login page from a browser or via curl/wget from the command line.
    Affected if The web interface is externally accessible without VPN or network segmentation, as this enables the remote unauthenticated attack vector.
  3. Review authentication configuration
    Check the authentication settings in the ArcSight Logger administration console to determine whether unauthenticated access is permitted to any endpoints or APIs.
    Affected if Unauthenticated access is allowed to any application endpoints, as this aligns with the CVE's unauthenticated exploitation requirement.

You are affected if your installed ArcSight Logger version is below 7.2.2 and the application is accessible to remote users without requiring authentication.

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 remediate these vulnerabilities.

Recommended fix High confidence

ArcSight Logger v7.2.2 or later

  1. 1. Backup all ArcSight Logger configurations, logs, and data before proceeding with the upgrade.
  2. 2. Download the ArcSight Logger v7.2.2 (or latest stable version) installer from the official Micro Focus Support Portal at portal.microfocus.com or www.microfocus.com.
  3. 3. Review the official upgrade guide and release notes for v7.2.2 for any specific prerequisites or migration procedures.
  4. 4. Test the upgrade in a non-production environment first to verify compatibility with your existing systems and integrations.
  5. 5. Schedule a maintenance window and stop all ArcSight Logger services before applying the upgrade.
  6. 6. Run the installer and follow the on-screen instructions to upgrade to v7.2.2 or later.
  7. 7. After upgrade completion, verify that all services start successfully and that the web interface is accessible.
  8. 8. Confirm the upgraded version by checking the ArcSight Logger interface or using the version check command.
Caveat Review release notes for any configuration or compatibility changes before upgrading; test in non-production environment first

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

Fix this in Arcsight Logger Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26330 — 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-26330 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