This page was not yet optimized for use on mobile devices.
CVE-2013-3525
Data ?
Vulnerability ID | CVE-2013-3525 |
---|---|
Published on | 10.05.2013 21:55 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:bestpractical:request_tracker:3.6.8:*:*:*:*:*:*:*,
cpe:2.3:a:bestpractical:request_tracker:3.6.10:*:*:*:*:*:*:*,
cpe:2.3:a:bestpractical:request_tracker:3.6.11:*:*:*:*:*:*:*,
cpe:2.3:a:bestpractical:request_tracker:3.8.3:*:*:*:*:*:*:*,
cpe:2.3:a:bestpractical:request_tracker:3.8.4:*:*:*:*:*:*:*,
cpe:2.3:a:bestpractical:request_tracker:3.8.7:*:*:*:*:*:*:*,
cpe:2.3:a:bestpractical:request_tracker:3.8.8:*:*:*:*:*:*:*,
cpe:2.3:a:bestpractical:request_tracker:3.8.9:*:*:*:*:*:*:*,
cpe:2.3:a:bestpractical:request_tracker:3.8.10:*:*:*:*:*:*:*,
cpe:2.3:a:bestpractical:request_tracker:3.8.11:*:*:*:*:*:*:*,
…
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.