# CVE-2015-3318: Privilege escalation in n/a

> Local attackers can exploit improper variable validation in CA Common Services to gain elevated privileges on UNIX systems.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-59xc-wp9m-f2jq

## What is CVE-2015-3318?

CVE-2015-3318 is a medium-severity vulnerability in n/a, published on 17 Jun 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CA Common Services, as used in CA Client Automation r12.5 SP01, r12.8, and r12.9; CA Network and Systems Management r11.0, r11.1, and r11.2; CA NSM Job Management Option r11.0, r11.1, and r11.2; CA Universal Job Management Agent; CA Virtual Assurance for Infrastructure Managers (aka SystemEDGE) 12.6, 12.7, 12.8, and 12.9; and CA Workload Automation AE r11, r11.3, r11.3.5, and r11.3.6 on UNIX, does not properly validate an unspecified variable, which allows local users to gain privileges via unknown vectors.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-3318?

It affects 6 products.


Products: Ca Client Automation, Ca Network and Systems Management, Ca Nsm Job Management Option, Ca Universal Job Management Agent, Ca Virtual Assurance for Infrastructure Managers, Ca Workload Automation Ae.

## How do I fix CVE-2015-3318?

No fix has been published for CVE-2015-3318 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-3318 being exploited?

There is no known exploitation of CVE-2015-3318 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-8391](https://insights.sbomify.com/CVE-2017-8391/): Information disclosure in n/a (medium 5.5)
- [CVE-2015-3317](https://insights.sbomify.com/CVE-2015-3317/): Memory corruption in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3318 and fix it if it is affected.

What it is: CVE-2015-3318 is a medium-severity vulnerability in n/a, published on 17 Jun 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3318 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-3318/ (Markdown: https://insights.sbomify.com/CVE-2015-3318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-3318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-3318
- OSV: https://osv.dev/vulnerability/CVE-2015-3318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-3318/
Summaries are generated and may contain mistakes; the official description above is the record.