Arcsight Enterprise Security ManagerApplication · Microfocus

CVE-2021-38127

MEDIUM · 6.1 CVSS v3.1 Published 2022-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Enterprise Security Manager, affecting versions 7.4.x and 7.5.x. The vulnerabilities could be remotely exploited resulting in 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

Cross-Site Scripting (XSS) vulnerability in Micro Focus ArcSight Enterprise Security Manager versions 7.4.x and 7.5.x. The vulnerability is remotely exploitable and allows attackers to inject malicious scripts through unsanitized user inputs, potentially compromising user sessions or stealing credentials.

MitigationApply vendor-supplied patches or upgrade to a patched version when available; implement input validation and output encoding as defense-in-depth measures.

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 Enterprise Security ManagerApplication
Affected:= 7.4= 7.5

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. Confirm ArcSight ESM installation
    Locate the Micro Focus ArcSight Enterprise Security Manager installation directory or running service on the system
    Affected if ArcSight ESM is not installed on the system
  2. Check installed version number
    Access the product's about page, version information in the administration console, or check the product version file in the installation directory
    Affected if The version is 7.4.x or 7.5.x (including all 7.4 and 7.5 point releases)
  3. Verify web interface accessibility
    Determine if the ArcSight ESM web interface (typically on ports 8443 or 8080) is exposed and reachable
    Affected if The web interface is accessible to network users without additional authentication barriers
  4. Identify user input points
    Review application logs or documentation for evidence of user-supplied input handling in the web interface
    Affected if The application processes user-supplied input without sanitization in web forms or parameters

A system is affected if Micro Focus ArcSight Enterprise Security Manager version 7.4.x or 7.5.x is installed and its web interface is accessible, as the XSS flaw exists in unsanitized user input handling.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches or upgrade to a patched version when available; implement input validation and output encoding as defense-in-depth measures.

Fix this in Arcsight Enterprise Security Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-38127 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-38127 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