CVE-2015-1497
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 · uneditedradexecd.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.
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 confidenceCritical pre-authentication remote code execution vulnerability in radexecd.exe service of Persistent Systems Radia Client Automation. The service listening on TCP port 3465 accepts crafted requests that allow unauthenticated remote attackers to execute arbitrary commands on the affected system.
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= 7.9= 8.1= 9.0= 9.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Radia Client Automation is installedCheck installed programs for 'Persistent Systems Radia Client Automation' or 'Radia Client Automation' in Windows Add/Remove Programs, or look for the radexecd.exe process in Task ManagerAffected if The product is installed and matches version 7.9, 8.1, 9.0, or 9.1
-
Determine the installed versionOpen Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check the program's About/Version information in the control panelAffected if The installed version is exactly 7.9, 8.1, 9.0, or 9.1
-
Check if radexecd.exe service is runningOpen Services console (services.msc) and look for a service named 'radexecd' or related Radia service, or run 'tasklist | findstr radexecd' in command promptAffected if The radexecd.exe process or service is running on the system
-
Verify if TCP port 3465 is listeningRun 'netstat -an | findstr 3465' or use PowerShell 'Get-NetTCPConnection -LocalPort 3465' to check if the service is bound to the networkAffected if Port 3465 shows as LISTENING or ESTABLISHED, indicating the vulnerable service is network-accessible
-
Confirm network exposure of the serviceCheck firewall rules or run 'netsh advfirewall firewall show rule name=all' to see if port 3465 is allowed through the Windows FirewallAffected if Port 3465 is open in the firewall and accessible from network hosts, making the vulnerability exploitable remotely
A user is affected if Radia Client Automation version 7.9, 8.1, 9.0, or 9.1 is installed with the radexecd.exe service running and listening on TCP port 3465, especially if that port is exposed to the network.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict network access to TCP port 3465 and apply vendor patches or upgrade to a patched version of Radia Client Automation.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1497 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-1497 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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