# What is CVE-2017-8391?

> CVE-2017-8391 is a medium-severity flaw (CVSS 5.5) in Client Automation from Ca, published on 6 May 2017. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.3%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2017-8391

## At a glance

- **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle.
- **Precursor Intelligence risk score:** 17 out of 100 (Info); action: Track. Kept up to date as the evidence changes.
- **Severity:** Medium (CVSS 5.5 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 0.3% (latest exploit-likelihood forecast)
- **Published:** 6 May 2017
- **Record last updated:** 20 April 2025
- **Main product:** Client Automation from Ca
- **Affected products:** 3

## What is CVE-2017-8391? In plain terms

An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data.

### The official description

The OS Installation Management component in CA Client Automation r12.9, r14.0, and r14.0 SP1 places an encrypted password into a readable local file during operating system installation, which allows local users to obtain sensitive information by reading this file after operating system installation.

### What kind of flaw is it?

- CWE-732: Incorrect Permission Assignment for Critical Resource

### How an attack on it works

- Where an attacker can be: Already on the device
- How hard it is to pull off: Easy: no special conditions
- Login needed first: An ordinary user account
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can read data

Severity vector: `CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`

## Is CVE-2017-8391 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.3%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 0.3%, 0.3%, 0.3%, 0.3%, 0.3%, 0.3%, 0.3%.

### Timeline

- 6 May 2017: Published
- 20 April 2025: Record last updated

### How Precursor Intelligence ranks it

CVE-2017-8391 scores **17 out of 100 (Info)**, with the action "Track".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2017-8391?

The published record lists 3 products.

- [Client Automation](https://www.precursorintelligence.com/product/ca/client_automation) by [Ca](https://www.precursorintelligence.com/vendors/ca) (Application): r12.9, r14.0, r14.0-sp1
- [Linux kernel](https://www.precursorintelligence.com/product/linux/linux_kernel) by [Linux](https://www.precursorintelligence.com/vendors/linux) (Operating system): all versions
- [Windows](https://www.precursorintelligence.com/product/microsoft/windows) by [Microsoft](https://www.precursorintelligence.com/vendors/microsoft) (Operating system): all versions

## How do I fix CVE-2017-8391?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [ca.com](https://www.ca.com/us/services-support/ca-support/ca-support-online/product-content/recommended-reading/security-notices/ca20170504-01-security-notice-for-ca-client-automation-os-installation-mgmt.html) (Vendor advisory)
- [securityfocus.com](http://www.securityfocus.com/bid/98344) (Third-party advisory, Vulnerability database)
- [securitytracker.com](http://www.securitytracker.com/id/1038410)

## Questions

### What is CVE-2017-8391?

CVE-2017-8391 is a medium-severity flaw in Client Automation from Ca, published on 6 May 2017. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data.

### How serious is CVE-2017-8391?

It scores 5.5 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2017-8391 is 17 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

### Is CVE-2017-8391 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.3%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2017-8391 affect?

For Client Automation from Ca: r12.9, r14.0, r14.0-sp1. The record lists 3 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2017-8391?

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2017-8391 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact