Spotfire Statistics Services: Improper Control of Generation of Code
CVE-2025-3115 is a critical-severity improper control of generation of code vulnerability in Spotfire Statistics Services from Spotfire, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 14.0.7 as the first without the flaw, so updating Spotfire Statistics Services to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.68% chance of exploitation within 30 days, higher than 53% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Spotfire Statistics Services to 14.0.7 or a later version.
- Update Spotfire Analyst to 14.0.6 or a later version.
- Update Deployment Kit used in Spotfire Server to 14.0.7 or a later version.
- Read the advisory on community.spotfire.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Spotfire | Spotfire Statistics Services | 14 up to, but not including, 14.0.7; 14.1.0; 14.2.0; 14.3.0; 14.4.0; 14.4.1 | 14.0.7 |
| Spotfire | Spotfire Analyst | 14.0 up to, but not including, 14.0.6; 14.1.0; 14.2.0; 14.3.0; 14.4.0; 14.4.1 | 14.0.6 |
| Spotfire | Deployment Kit used in Spotfire Server | 14.0 up to, but not including, 14.0.7; 14.1.0; 14.2.0; 14.3.0; 14.4.0; 14.4.1 | 14.0.7 |
| Spotfire | Spotfire Desktop | 14.4 up to, but not including, 14.4.2 | 14.4.2 |
| Spotfire | Spotfire for AWS Marketplace | Not specified in the record | Not stated |
| Spotfire | Spotfire Enterprise Runtime for R - Server Edition | 1.17 up to, but not including, 1.17.7; 1.18.0; 1.19.0; 1.20.0; 1.21.0; 1.21.1 | 1.17.7 |
| Spotfire | Spotfire Service for Python | 1.17 up to, but not including, 1.17.7; 1.18.0 through 1.21.1 | 1.17.7 |
| Spotfire | Spotfire Service for R | 1.17 up to, but not including, 1.17.7; 1.18.0 through 1.21.1 | 1.17.7 |
| TIBCO | Spotfire Enterprise Runtime For R | before 6.1.5; before 1.17.7; 1.18.0; 1.19.0; 1.20.0; 1.21.0; 1.21.1 | 6.1.5, 1.17.7 |
| TIBCO | Spotfire Deployment Kit | before 14.0.7; 14.1.0; 14.2.0; 14.3.0; 14.4.0; 14.4.1 | 14.0.7 |
| TIBCO | Spotfire Analytics Platform | before 14.4.2 | 14.4.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.4 | Critical | CNA (tibco.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
Injection Vulnerabilities: Attackers can inject malicious code, potentially gaining control over the system executing these functions. Additionally, insufficient validation of filenames during file uploads can enable attackers to upload and execute malicious files, leading to arbitrary code execution
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Spotfire Statistics Services
- 9.4 Critical severity
Recent Improper Control of Generation of Code vulnerabilities
- 9.9 Critical severity
- 9.9 Critical severity
- 8.5 High severity
- 9.8 Critical severity
Langflow Missing Authentication Exploited
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.