dbcve.org
Ca Workload Automation AeApplication · Broadcom

CVE-2016-9795

HIGH · 7.8 CVSS v3.1 Published 2017-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
The casrvc program in CA Common Services, as used in CA Client Automation 12.8, 12.9, and 14.0; CA SystemEDGE 5.8.2 and 5.9; CA Systems Performance for Infrastructure Managers 12.8 and 12.9; CA Universal Job Management Agent 11.2; CA Virtual Assurance for Infrastructure Managers 12.8 and 12.9; CA Workload Automation AE 11, 11.3, 11.3.5, and 11.3.6 on AIX, HP-UX, Linux, and Solaris allows local users to modify arbitrary files and consequently gain root privileges via vectors related to insufficient validation.

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

The casrvc program in CA Common Services suffers from insufficient input validation, allowing local users to modify arbitrary files on the system. By exploiting this flaw, a local attacker can overwrite system files or configurations to escalate privileges to root.

MitigationApply vendor patches for affected CA products (Client Automation 12.8/12.9/14.0, SystemEDGE 5.8.2/5.9, Systems Performance 12.8/12.9, Universal Job Management Agent 11.2, Virtual Assurance 12.8/12.9, Workload Automation AE 11/11.3/11.3.5/11.3.6). Restrict local access to trusted users until patches are applied.

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
Ca Workload Automation AeApplication
Affected:= 11.0= 11.3= 11.3.5= 11.3.6
Client AutomationApplication
Affected:= 12.8= 12.9= 14.0
SystemedgeWeb browser
Affected:= 5.8.2= 5.9
Systems Performance For Infrastructure ManagersApplication
Affected:= 12.8= 12.9
Universal Job Management AgentApplication
Affected:= 11.2
Virtual Assurance For Infrastructure ManagersApplication
Affected:= 12.8= 12.9

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Locate the casrvc binary
    Search for the casrvc executable in common CA Common Services installation directories such as /opt/CA, /opt/CA/SharedComponents, or use 'find / -name casrvc -type f 2>/dev/null' to locate it
    Affected if The casrvc binary exists on the system and is part of an unpatched CA Common Services installation
  2. Identify the CA Common Services version
    Run 'casrvc -v' or check the installation manifest, README, or version file in the CA Common Services directory to determine the installed version
    Affected if The CA Common Services version matches one of the affected versions: 11.0, 11.3, 11.3.5, or 11.3.6 for Workload Automation AE; 12.8, 12.9, 14.0 for Client Automation; 5.8.2 or 5.9 for SystemEDGE; 12.8 or 12.9 for Systems Performance or Virtual Assurance; or 11.2 for Universal Job Management Agent
  3. Verify file permissions on casrvc
    Run 'ls -la <path_to_casrvc>' to check the ownership and permissions of the casrvc binary
    Affected if The casrvc binary is owned by root and has setuid permissions, or is accessible to untrusted local users without proper restrictions
  4. Confirm casrvc service presence
    Check if the casrvc service is registered and running using 'ps aux | grep casrvc' or system service commands like 'systemctl list-units' or 'service --status-all'
    Affected if The casrvc service is running and accepts input that could be manipulated by local users to write to arbitrary file locations

A system is affected if the casrvc binary from CA Common Services is present and its version matches one of the affected product versions listed in the CVE, with permissions that permit untrusted local users to trigger the file overwrite vulnerability.

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 patches for affected CA products (Client Automation 12.8/12.9/14.0, SystemEDGE 5.8.2/5.9, Systems Performance 12.8/12.9, Universal Job Management Agent 11.2, Virtual Assurance 12.8/12.9, Workload Automation AE 11/11.3/11.3.5/11.3.6). Restrict local access to trusted users until patches are applied.

Fix this in Ca Workload Automation Ae 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-2016-9795 — 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-2016-9795 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