-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
urllib.error.HTTPError: HTTP Error 404: Not Found #11
Comments
So I spun up an Ubuntu 20.04 VM and that has Python 3.8.2, and I still get the same error. |
I am getting a similar error (slightly different line numbers in some of the library stuff, probably owing to python 3.7 vs. 3.6?) when running against python 3.7.7 on macOS. I git cloned the repo directly from here... My python3 is from homebrew.
|
I updated UPnP stack to handle exceptions. can you retry? |
Some improvement but a different failure for me now.
For the record, I do have a UPnP "gateway" device, but it is pfSense running miniupnpd (and I'm not sure if that fully complies to the official UPnP spec, don't even know if it has an SSDP endpoint). The device it appears to have died on here (192.168.42.4) is not my gateway/router, it's a Synology NAS (not even sure if that has a UPnP daemon in it... if it does, it would just be a multimedia device endpoint for video discovery, that kind of thing - not a router) |
I think location header is empty. I broaded the catch. can you try again? |
I just re-pulled, no change, exact same error as before. |
Just did a pull... Still have an error with 18.04 (Python v. 3.6.9)
Getting an error with 20.04 (Python v. 3.8.3)
|
it almost feels like Yunus is debugging poor UPnP implementations in consumer devices at this point (e.g. streaming media sources / etc, like my Synology NAS)... @JSylvia007 I'm guessing that none of the IPs you're seeing it choke on are your actual router / WAN device? |
That could very well be. I haven't seen it make it to my router yet. It always crashes before that. |
I get the same error. Also too, the amount of devices being found on startup varies. 3 to 14 everything there... |
Hi there are too many devices. I broaded exception handling. can you try again? |
Much improved, seems to have run to completion, but still some errors and definitely isn't showing everything it found. Here's full output:
|
Can you try again? there are too many exception point. I don't know why upnp stacks are not handling this exceptions!! |
Full completion! I did not run the test / verify if services are vulnerable but going to try that next. Here's the full output (I edited some hostnames / device names again, in square brackets):
I am not sure why the Philips hue bridge showed up so many times... if it was finding different ports or something that might make sense, but it seems to just be showing the same endpoint over and over? Kind of strange. |
Running the online verify also worked. Seems like two of the endpoints on the Synology NAS are vulnerable. The 8 on the "Denon AV Receiver 1" (I can't remember the model number off-hand) are all vulnerable as well. The 3 services on the Denon X3200W are "unverified", as are the 3 endpoints on the pfSense router/gateway. |
Hi |
Sure, the confirmed vulnerable AVR for me is a Denon X3500H. The X3200W is showing "unverified," so I guess that one may not be? The Synology vulnerability should impact (at least) any Intel-based Synology NAS (mine is running the latest available OS for the DS412+ which I believe is also used on a bunch of newer units). But neither of these are gateway devices at least... and it's good to see that miniupnpd on pfSense (which is a gateway) seems safe. You may want to leave this open until others who were having problems get a chance to test, just because it worked for me may not mean their errors are all resolved. |
Can you share vulnerable services' server header. It may contain detailed device info like version |
Sure, here is the header info from the items listed as vulnerable:
And here are the ones with failure codes (and they match the "unverified" list):
Final output was:
More than a little ironic that stuff running Linux internally has the problem, while I see no Microsoft devices on the list. I have two XBox OneXs in the house, but both were powered off during my tests... I also have a couple Windows laptops, those were both on but probably in sleep mode at the time. |
Thanks. Added |
So the outcome is now stable with 7 upnp devices, however I still get the 404 |
Sometimes it finds more hosts, but mostly it just fails with the below stacktrace.
Ubuntu 18.04 w/ Python3 VENV, Python v3.6.9
The text was updated successfully, but these errors were encountered: