| Version | |
|---|---|
| tracy-client.0.6 (latest) | |
| tracy-client.0.5.2 | |
| tracy-client.0.5.1 | |
| tracy-client.0.5 | |
| tracy-client.0.4 | |
| tracy-client.0.3 | |
| tracy-client.0.2 | |
| tracy-client.0.1 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | tracy-client.0.1 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | tracy-client.0.2 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | tracy-client.0.3 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | tracy-client.0.5.2 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | tracy-client.0.4 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | tracy-client.0.5.1 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | tracy-client.0.6 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | tracy-client.0.5 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | tracy-client.0.5.2 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-headers | tracy-client.0.5 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-headers | tracy-client.0.6 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-headers | tracy-client.0.4 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-headers | tracy-client.0.5.1 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-headers | tracy-client.0.3 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-headers | tracy-client.0.2 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-headers | tracy-client.0.1 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-headers | tracy-client.0.1 | Flexera Software LLC | Unknown | CVE-2017-16914 | 1/31/2018 |
| linux-headers | tracy-client.0.5.2 | Flexera Software LLC | Unknown | CVE-2017-16914 | 1/31/2018 |
| linux-headers | tracy-client.0.5 | Flexera Software LLC | Unknown | CVE-2017-16914 | 1/31/2018 |
| linux-headers | tracy-client.0.6 | Flexera Software LLC | Unknown | CVE-2017-16914 | 1/31/2018 |