CVE-2019-3486
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 · uneditedMitigates a stored cross site scripting issue in ArcSight Security Management Center versions prior to 2.9.1
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 confidenceStored cross-site scripting (XSS) vulnerability in ArcSight Security Management Center allowing attackers to inject malicious scripts that persist on the server and execute in authenticated users' browsers when viewing compromised content. The vulnerability affects versions prior to 2.9.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< 2.9.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify ArcSight Management Center installationLocate the ArcSight Management Center installation directory, typically under /opt/arcsight/mgmt or C:\arcsight\mgmt on Windows servers. Check for the presence of the ArcSight Management Center software.Affected if The product is not found in standard installation directories.
-
Determine installed versionCheck the version file or About section in the ArcSight Management Center admin interface. The version is often displayed on the login page or in the administrator settings panel. You can also check version files in the installation directory, such as version.properties or a similar versioninfo file.Affected if The displayed version number is lower than 2.9.1.
-
Verify web interface accessibilityAttempt to access the ArcSight Management Center web console via browser at the configured URL (typically https://hostname:8443/mgmt). Confirm the login page loads successfully.Affected if The web interface is accessible and responds to requests.
-
Inspect stored content for suspicious scriptsReview user-generated content, saved searches, dashboard configurations, or any fields that accept custom input within the ArcSight Management Center console. Look for unexpected script tags, javascript: URIs, or event handlers in stored data.Affected if Malicious script payloads are found persisted in application fields or configurations.
You are affected if your installed ArcSight Management Center version is below 2.9.1 and the web interface is accessible, as the stored XSS vulnerability can be exploited in the authenticated web console.
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.
From vendor data2.9.1
Upgrade ArcSight Security Management Center to version 2.9.1 or later to apply the security patch that addresses the stored XSS vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2019-3486 — 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-2019-3486 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