dbcve.org
Arcsight Management CenterApplication · Microfocus

CVE-2020-25835

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-09
Fix available
A fix is available. Upgrade to 2.9.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A potential vulnerability has been identified in Micro Focus ArcSight Management Center. The vulnerability could be remotely exploited resulting in stored Cross-Site Scripting (XSS).

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

Stored Cross-Site Scripting (XSS) vulnerability in Micro Focus ArcSight Management Center. The vulnerability can be remotely exploited by injecting malicious scripts that are persistently stored on the server and executed when other users access the affected functionality.

MitigationImplement proper input validation, output encoding, and sanitization of user-supplied data across all input fields in ArcSight Management Center. Apply available vendor patches when released.

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 Management CenterApplication
Affected:>= 2.9.0, < 2.9.6

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm ArcSight Management Center installation
    Locate the ArcSight Management Center application in your environment. Common installation paths include /opt/arcsight/mc or C:\Program Files\ArcSight\Management Center. Check for the 'arcsight-management-center' or 'arcsight-mc' directory structure.
    Affected if The product is not installed in your environment.
  2. Identify installed version
    Access the ArcSight Management Center web interface and navigate to Help > About, or check the version file in the installation directory. Common version file locations: <install_dir>/lib/arcsight-mc-version.jar or /opt/arcsight/mc/arcsight-mc-version.properties. You can also run: arcsight mcversion from the command line if available.
    Affected if Unable to determine version from the application or installation files.
  3. Compare version against affected range
    Review the identified version number. The affected range is version 2.9.0 through any version lower than 2.9.6. Check if your version falls within >= 2.9.0 and < 2.9.6.
    Affected if Your installed version is 2.9.0, 2.9.1, 2.9.2, 2.9.3, 2.9.4, or 2.9.5 (any version >= 2.9.0 but < 2.9.6).

You are affected if ArcSight Management Center is installed and the version falls between 2.9.0 and 2.9.5 inclusive.

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 2.9.6 or later
Fixed in 2.9.6
Interim mitigation

Implement proper input validation, output encoding, and sanitization of user-supplied data across all input fields in ArcSight Management Center. Apply available vendor patches when released.

Recommended fix Moderate confidence

ArcSight Management Center 2.9.6 or later

  1. 1. Review the Micro Focus ArcSight Management Center upgrade documentation on community.microfocus.com or support.microfocus.com
  2. 2. Back up the current ArcSight Management Center configuration and data
  3. 3. Download the fixed version (2.9.6 or later) from the Micro Focus software download portal
  4. 4. Follow the standard ArcSight Management Center upgrade procedure for your deployment type
  5. 5. After upgrade, verify the Management Center web interface is accessible and functioning
  6. 6. Test that the previously vulnerable functionality is working correctly

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

Fix this in Arcsight Management Center 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-2020-25835 — 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-2020-25835 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