18015.0 |
333 |
192.168.1.252 |
1900 |
192.168.1.69 |
1829 |
Potentially Bad Traffic |
ET INFO |
UPnP Discovery Search Response - CVE-2012-5958 and CVE-2012-5959 Vulnerable UPnP device M1 |
2 |
18015.0 |
334 |
192.168.1.252 |
1900 |
192.168.1.69 |
1829 |
Potentially Bad Traffic |
ET INFO |
UPnP Discovery Search Response - CVE-2012-5958 and CVE-2012-5959 Vulnerable UPnP device M1 |
2 |
18022.0 |
457 |
192.168.1.252 |
1900 |
192.168.1.69 |
64592 |
Potentially Bad Traffic |
ET INFO |
UPnP Discovery Search Response - CVE-2012-5958 and CVE-2012-5959 Vulnerable UPnP device M1 |
2 |
18022.0 |
459 |
192.168.1.252 |
1900 |
192.168.1.69 |
64592 |
Potentially Bad Traffic |
ET INFO |
UPnP Discovery Search Response - CVE-2012-5958 and CVE-2012-5959 Vulnerable UPnP device M1 |
2 |
18023.0 |
471 |
192.168.1.252 |
1900 |
192.168.1.69 |
64595 |
Potentially Bad Traffic |
ET INFO |
UPnP Discovery Search Response - CVE-2012-5958 and CVE-2012-5959 Vulnerable UPnP device M1 |
2 |
18023.0 |
472 |
192.168.1.252 |
1900 |
192.168.1.69 |
64595 |
Potentially Bad Traffic |
ET INFO |
UPnP Discovery Search Response - CVE-2012-5958 and CVE-2012-5959 Vulnerable UPnP device M1 |
2 |