# CVE-2015-1497: Command injection in n/a

> Remote attackers can execute arbitrary commands on Persistent Systems Radia Client Automation servers via crafted network requests.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hp4v-x6cx-hqr2

## What is CVE-2015-1497?

CVE-2015-1497 is a critical command injection vulnerability in n/a, published on 16 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

radexecd.exe in Persistent Systems Radia Client Automation (RCA) 7.9, 8.1, 9.0, and 9.1 allows remote attackers to execute arbitrary commands via a crafted request to TCP port 3465.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Persistent Systems Radia Client Automation.

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

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

## Is CVE-2015-1497 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1497 exists.

Public exploit code:

- HP Client Automation Command Injection (metasploit)
- HP Client - Automation Command Injection (Metasploit) (exploitdb)
- Persistent Systems Client Automation - Command Injection Remote Code Execution (Metasploit) (exploitdb)
- HP Client 9.1/9.0/8.1/7.9 - Command Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-1498](https://insights.sbomify.com/CVE-2015-1498/): Missing authorization in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-1497 is a critical command injection vulnerability in n/a, published on 16 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1497 exists.

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-1497/ (Markdown: https://insights.sbomify.com/CVE-2015-1497/index.md)
```

## Sources

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

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