18001.0 |
5 |
192.168.1.252 |
1900 |
192.168.1.69 |
8994 |
Potentially Bad Traffic |
ET INFO |
UPnP Discovery Search Response - CVE-2012-5958 and CVE-2012-5959 Vulnerable UPnP device M1 |
2 |
18001.0 |
6 |
192.168.1.252 |
1900 |
192.168.1.69 |
8994 |
Potentially Bad Traffic |
ET INFO |
UPnP Discovery Search Response - CVE-2012-5958 and CVE-2012-5959 Vulnerable UPnP device M1 |
2 |
18041.0 |
534 |
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 |
18041.0 |
535 |
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 |
18045.0 |
579 |
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 |
18045.0 |
580 |
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 |
18054.0 |
778 |
192.168.1.252 |
1900 |
192.168.1.69 |
8994 |
Potentially Bad Traffic |
ET INFO |
UPnP Discovery Search Response - CVE-2012-5958 and CVE-2012-5959 Vulnerable UPnP device M1 |
2 |
18054.0 |
779 |
192.168.1.252 |
1900 |
192.168.1.69 |
8994 |
Potentially Bad Traffic |
ET INFO |
UPnP Discovery Search Response - CVE-2012-5958 and CVE-2012-5959 Vulnerable UPnP device M1 |
2 |