| CVE-2020-4254 |
IBM Security Guardium Big Data Intelligence 1.0 (SonarG) uses weaker than expected cryptographic algorithms that could…
|
5.9
Moyenne
|
16 oct. 2020 |
| CVE-2019-4339 |
IBM Security Guardium Big Data Intelligence (SonarG) 4.0 uses weaker than expected cryptographic algorithms that could…
|
5.9
Moyenne
|
28 oct. 2019 |
| CVE-2019-4330 |
IBM Security Guardium Big Data Intelligence (SonarG) 4.0 does not set the secure attribute for cookies in HTTPS…
|
3.1
Faible
|
28 oct. 2019 |
| CVE-2019-4329 |
IBM Security Guardium Big Data Intelligence (SonarG) 4.0 uses incomplete blacklisting for input validation which…
|
4.3
Moyenne
|
28 oct. 2019 |
| CVE-2019-4314 |
IBM Security Guardium Big Data Intelligence (SonarG) 4.0 stores sensitive information in cleartext within a resource…
|
5.9
Moyenne
|
28 oct. 2019 |
| CVE-2019-4311 |
IBM Security Guardium Big Data Intelligence (SonarG) 4.0 discloses sensitive information to unauthorized users
|
5.3
Moyenne
|
28 oct. 2019 |
| CVE-2019-4307 |
IBM Security Guardium Big Data Intelligence (SonarG) 4.0 stores user credentials in plain in clear text which can be…
|
5.1
Moyenne
|
28 oct. 2019 |
| CVE-2019-4309 |
IBM Security Guardium Big Data Intelligence (SonarG) 4.0 uses hard coded credentials which could allow a local user to…
|
5.9
Moyenne
|
28 oct. 2019 |
| CVE-2019-4306 |
IBM Security Guardium Big Data Intelligence (SonarG) 4.0 specifies permissions for a security-critical resource which…
|
6.5
Moyenne
|
28 oct. 2019 |
| CVE-2019-4338 |
IBM Security Guardium Big Data Intelligence 4.0 (SonarG) does not properly restrict the size or amount of resources that…
|
7.5
Élevée
|
20 août 2019 |
| CVE-2019-4340 |
IBM Security Guardium Big Data Intelligence 4.0 (SonarG) is vulnerable to an XML External Entity Injection (XXE)…
|
7.1
Élevée
|
20 août 2019 |
| CVE-2019-4310 |
IBM Security Guardium Big Data Intelligence 4.0 (SonarG) uses an inadequate account lockout setting that could allow a…
|
7.5
Élevée
|
20 août 2019 |
| CVE-2018-1369 |
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 stores sensitive information in URL parameters
|
3.7
Faible
|
29 mai 2018 |
| CVE-2018-1376 |
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 is vulnerable to cross-site scripting
|
6.1
Moyenne
|
29 mai 2018 |
| CVE-2018-1375 |
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 does not renew a session variable after a successful…
|
5.9
Moyenne
|
29 mai 2018 |
| CVE-2018-1370 |
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 specifies permissions for a security-critical resource in a way…
|
4.2
Moyenne
|
29 mai 2018 |
| CVE-2017-1768 |
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 generates an error message that includes sensitive…
|
4.3
Moyenne
|
29 mai 2018 |
| CVE-2018-1373 |
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 uses an inadequate account lockout setting that could allow a…
|
7.5
Élevée
|
2 mars 2018 |
| CVE-2018-1425 |
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 uses weaker than expected cryptographic algorithms that could…
|
Non notée
|
27 févr. 2018 |
| CVE-2018-1372 |
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 does not require that users should have strong passwords by…
|
Non notée
|
27 févr. 2018 |
| CVE-2018-1377 |
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 stores user credentials in plain in clear text which can be…
|
Non notée
|
26 févr. 2018 |
| CVE-2017-1774 |
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 discloses sensitive information to unauthorized users
|
Non notée
|
26 févr. 2018 |