# CVE-2015-1498: Missing authorization in n/a

> Remote attackers can enumerate users and modify role assignments due to missing authorization checks in Persistent Systems Radia Client Automation.

- **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-v4mp-6mcf-frrc

## What is CVE-2015-1498?

CVE-2015-1498 is a critical missing authorization 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

Persistent Systems Radia Client Automation does not properly restrict access to certain request, which allows remote attackers to (1) enumerate user accounts via a getUsers request, (2) assign a role to a user account via an addAssigneesToRole request, (3) remove a role from a user account via a removeAssigneesFromRole request, or (4) have other unspecified impact.

Weakness: CWE-264

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

It affects 1 product.


Products: Persistent Systems Radia Client Automation.

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

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

## Is CVE-2015-1498 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-1497](https://insights.sbomify.com/CVE-2015-1497/): Command injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-1498 is a critical missing authorization 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: There is no known exploitation of CVE-2015-1498 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-1498/ (Markdown: https://insights.sbomify.com/CVE-2015-1498/index.md)
```

## Sources

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

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