dbcve.org
Radia Client AutomationApplication · Persistent Systems

CVE-2015-1498

HIGH · 10.0 CVSS v2.0 Published 2015-02-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
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.

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 · high confidence

Persistent Systems Radia Client Automation fails to enforce proper access controls on specific API requests, allowing unauthenticated remote attackers to enumerate user accounts via getUsers, and modify user roles through addAssigneesToRole and removeAssigneesFromRole requests. This represents a critical authorization bypass vulnerability enabling potential privilege escalation.

MitigationImplement proper authentication and role-based authorization checks on all administrative API endpoints, particularly user enumeration and role management functions. Apply vendor-provided patches immediately.

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
Radia Client AutomationApplication
Affected:all versions

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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Confirm Radia Client Automation is installed
    Check for the product by looking for installation directories (typically under C:\Program Files\Persistent Systems or similar), or look for the Radia service running on common ports (80, 443, 8080). Use 'netstat -ano' to identify listening services related to Radia.
    Affected if The product is installed and running with its web/API interface accessible on the network.
  2. Identify the API endpoint accessibility
    Locate the API endpoint URL for the application. Common paths include /radia/, /api/, or the main web interface. Use a browser or curl to access the base URL: curl -k http://<server>/radia/ or https://<server>/radia/
    Affected if The web interface or API endpoint returns HTTP 200 without requiring login credentials.
  3. Test user enumeration vulnerability (getUsers)
    Send a direct API request to the getUsers endpoint without authentication. Example: curl -k -X POST http://<server>/radia/api/getUsers or curl -k http://<server>/radia/api/user/list
    Affected if The response returns a list of user accounts without requiring any authentication credentials.
  4. Test role modification vulnerability (addAssigneesToRole)
    Send a direct API request to addAssigneesToRole without authentication. Example: curl -k -X POST -H 'Content-Type: application/json' -d '{"role":"admin","users":["testuser"]}' http://<server>/radia/api/role/addAssignees
    Affected if The request is processed without returning an authentication or authorization error.
  5. Test role removal vulnerability (removeAssigneesFromRole)
    Send a direct API request to removeAssigneesFromRole without authentication. Example: curl -k -X POST -H 'Content-Type: application/json' -d '{"role":"admin","users":["testuser"]}' http://<server>/radia/api/role/removeAssignees
    Affected if The request is processed without returning an authentication or authorization error.

If the Radia Client Automation web/API interface is exposed and any of the getUsers, addAssigneesToRole, or removeAssigneesFromRole endpoints respond without requiring authentication, the environment is vulnerable to CVE-2015-1498.

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

Implement proper authentication and role-based authorization checks on all administrative API endpoints, particularly user enumeration and role management functions. Apply vendor-provided patches immediately.

Fix this in Radia Client Automation 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-2015-1498 — 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-2015-1498 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