Planning Analytics Local vulnerabilitiesRanked by how likely they are to be used.
Planning Analytics Local is made by IBM. We track 25 published vulnerabilities in it, across 13 versions. None of them is on the list of flaws known to be exploited today. If you run Planning Analytics Local, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Planning Analytics Local vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Planning Analytics Local's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Planning Analytics Local flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.4%CVE-2020-4670Critical
IBM Planning Analytics Local 2.0 connects to a Redis server.
- 1.9%CVE-2020-4669Critical
IBM Planning Analytics Local 2.0 connects to a MongoDB server.
- 1.2%CVE-2020-4644Medium
IBM Planning Analytics Local 2.0.0 through 2.0.9.1 could allow a remote attacker to hijack the clicking action of the victim.
- 1.1%CVE-2021-29739Medium
IBM Planning Analytics Local 2.0 could allow a remote attacker to obtain sensitive information when a stack trace is returned in the browser.
- 1.0%CVE-2020-4985High
IBM Planning Analytics Local 2.0 could allow an attacker to obtain sensitive information due to accepting body parameters in a query.
- 0.9%CVE-2018-1676Medium
IBM Planning Analytics 2.0.0 through 2.0.4 is vulnerable to cross-site scripting.
- 0.8%CVE-2020-4503Medium
IBM Planning Analytics Local 2.0 is vulnerable to cross-site scripting.
- 0.8%CVE-2020-4649Medium
IBM Planning Analytics Local 2.0.9.2 and IBM Planning Analytics Workspace 57 could expose data to non-privleged users by not invalidating TM1Web user sessions.
- 0.8%CVE-2020-4367High
IBM Planning Analytics Local 2.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
- 0.7%CVE-2020-4366Medium
IBM Planning Analytics Local 2.0 is vulnerable to cross-site scripting.
Running Planning Analytics Local? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
IBM Planning Analytics Local 2.0 connects to a Redis server. The Redis server, an in-memory data structure store, running on the remote host is not protected by password authentication. A remote attacker can exploit this to gain unauthorized access to the server. IBM X-Force ID: 186401.
- Matched to
- Planning Analytics Local on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 25 published vulnerabilities listed under the name Planning Analytics Local, across 13 versions.
None of Planning Analytics Local's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Planning Analytics Local. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.