-
Notifications
You must be signed in to change notification settings - Fork 14.6k
CVE-2019-1663 - Add support for RV110W and RV215W models. #12133
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
Conversation
|
Hi, @qkaiser. I probably won't be able to get the new devices to test, so I'm relying on you for that. :)
Yep! You can set |
Thanks for trusting me with this.
Great ! I just did that in the latest commit. |
|
I'll get this updated with #12223 once that lands, then I'll land this. |
Release NotesThe |
This pull request add support for Cisco RV110W and RV215W models that are affected by the same issue than RV130 (CVE-2019-1663).
I wrote a check function that fingerprint firmware versions based on a file that is available to unauthenticated users. This is the best method I could find given the httpd server does not leak information through headers. If you can think of a better method let me know :)
I used the existing method of deprecation given that #12027 hasn't landed yet. I'll let @wvu-r7 refactor the module with proper deprecation method when it lands.
One open question is whether it is possible to set a default payload based on the chosen target ? So that it uses
linux/armle/meterpreter_reverse_tcpfor RV130 andlinux/mipsle/meterpreter_reverse_tcpfor RV110W/RV215W.Verification
Cisco RV110W (firmware version 1.1.0.9)
Cisco RV110W (firmware version 1.2.0.9)
Cisco RV110W (firmware version 1.2.0.10)
Cisco RV110W (firmware version 1.2.1.4)
Cisco RV110W (firmware version 1.2.1.7)
Cisco RV215W (firmware version 1.1.0.5)
Cisco RV215W (firmware version 1.1.0.6)
Cisco RV215W (firmware version 1.2.0.14)
Cisco RV215W (firmware version 1.2.0.15)
Cisco RV215W (firmware version 1.3.0.7)
Cisco RV215W (firmware version 1.3.0.8)
Updates #11613.