CVE-2015-6030
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 · uneditedHP ArcSight Logger 6.0.0.7307.1, ArcSight Command Center 6.8.0.1896.0, and ArcSight Connector Appliance 6.4.0.6881.3 use the root account to execute files owned by the arcsight user, which might allow local users to gain privileges by leveraging arcsight account access.
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 confidenceHP ArcSight products execute files owned by the arcsight user using the root account, creating a local privilege escalation vulnerability. A local user with arcsight account access could manipulate or replace these files to execute arbitrary code with root privileges.
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.4.0.6881.3= 6.0.0.7307.1= 6.8.0.1896.0<= 7.1.3= 4.0<= 2.0<= 6.5CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 product and versionRun 'arcsight version' or check /opt/arcsight/console/current/lib/arcsight.jar manifest, or look for version files in /opt/arcsight/ directoriesAffected if The installed version matches one of the affected versions: Connector Appliance <=6.4.0.6881.3, Logger 6.0.0.7307.1, Command Center 6.8.0.1896.0, Connectors <=7.1.3, Express 4.0, Management Center <=2.0, or Enterprise Security Manager <=6.5
-
Verify the arcsight user existsCheck for the arcsight user with command 'id arcsight' or look in /etc/passwdAffected if The arcsight user exists on the system, indicating an ArcSight product is installed
-
Find files owned by arcsight in executable pathsRun 'find /opt /var /usr -user arcsight -type f \( -perm -u+x -o -perm -g=x -o -perm -o=x \) 2>/dev/null' to locate executable files owned by the arcsight userAffected if Executable files owned by the unprivileged arcsight user are found in system paths
-
Check for root-owned cron or init scripts that execute arcsight-owned filesExamine /etc/cron* directories, /etc/init.d/, and systemd service files for commands that run files from paths like /opt/arcsight/ as rootAffected if Cron jobs, init scripts, or systemd services run files owned by the arcsight user with root privileges
-
Audit the execution chain for improper privilege separationReview scripts in /opt/arcsight/ and check which ones are invoked by root-owned processes; use 'ps aux' and 'ls -la' to trace execution pathsAffected if Root-owned processes are executing or sourcing files owned by the arcsight user
A system is affected if it runs any ArcSight product from the affected version list AND has executable files owned by the unprivileged arcsight user that are invoked by root-owned processes such as cron jobs, init scripts, or services.
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 dataRestrict file permissions so root does not execute files owned by unprivileged users; audit and correct the execution chain to use proper privilege separation.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6030 — 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-2015-6030 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