CVE-2019-3485
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 Logger versions prior to 6.7.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 Logger allows attackers to inject malicious scripts that persist on the server and execute in browsers of other users viewing the affected content. The vulnerability exists in versions prior to 6.7.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< 6.7.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 installed ArcSight Logger versionAccess the ArcSight Logger web interface and navigate to 'Administration' > 'System' > 'General' to view the product version, or run 'arcsight logger version' from the command line if you have CLI accessAffected if The displayed version is below 6.7.1 (e.g., 6.7.0, 6.6.x, or earlier)
-
Confirm web interface is enabledVerify that the ArcSight Logger web console is accessible by attempting to reach the login page at the configured hostname or IP on the default ports (typically 443 or 8443)Affected if The web interface responds and accepts authentication - this means the vulnerable attack surface is exposed
-
Review web access logs for XSS injection patternsExamine ArcSight Logger server logs (typically in /opt/arcsight/logger/data/logs/ or the configured log directory) for suspicious request patterns containing HTML tags such as <script>, <img>, or javascript: in query parameters or form submissionsAffected if Log entries contain unsanitized user-supplied scripts or HTML that could indicate exploitation attempts or vulnerable input fields
You are affected if ArcSight Logger version is below 6.7.1 AND the web interface is accessible to users or attackers
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 data6.7.1
Upgrade ArcSight Logger to version 6.7.1 or later to remediate the stored XSS vulnerability. Follow standard upgrade procedures and verify the patch is applied successfully.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3485 — 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-3485 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