This page was not yet optimized for use on mobile devices.
CVE-2010-3322
Data ?
| Vulnerability ID | CVE-2010-3322 |
|---|---|
| Published on | 14.09.2010 17:00 |
| Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:splunk:splunk:4.0:*:*:*:*:*:*:*,
cpe:2.3:a:splunk:splunk:4.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:splunk:splunk:4.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:splunk:splunk:4.0.3:*:*:*:*:*:*:*,
cpe:2.3:a:splunk:splunk:4.0.4:*:*:*:*:*:*:*,
cpe:2.3:a:splunk:splunk:4.0.5:*:*:*:*:*:*:*,
cpe:2.3:a:splunk:splunk:4.0.6:*:*:*:*:*:*:*,
cpe:2.3:a:splunk:splunk:4.0.7:*:*:*:*:*:*:*,
cpe:2.3:a:splunk:splunk:4.0.8:*:*:*:*:*:*:*,
cpe:2.3:a:splunk:splunk:4.0.9:*:*:*:*:*:*:*,
…
Vulnerable certificates ?
The CVE was matched to the following certificates. This means the vulnerability likely affects said certified devices. However, this is an automated process that may have false positives and negatives.