# Winbox vulnerability: please upgrade

**URL:** <https://forum.mikrotik.com/t/winbox-vulnerability-please-upgrade/122004>\
**Category:** Announcements\
**Created:** [August 2, 2018, 10:34am UTC](https://forum.mikrotik.com/t/winbox-vulnerability-please-upgrade/122004 "2018-08-02T10:34:07Z")\
**Posts on this page:** 1\
**Showing post:** 103

<div class="post-metadata">

**Author:** ![excession](https://forum.mikrotik.com/letter_avatar/excession/32/6_449c533f586939b6e5f246632a46421f.png) [@excession](https://forum.mikrotik.com/u/excession)\
**Post date:** [August 8, 2018, 12:19am UTC](https://forum.mikrotik.com/t/winbox-vulnerability-please-upgrade/122004/103 "2018-08-08T00:19:14Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > Is he trying to use Winbox to connect
> 
> No idea, but possible.
> 
> > [@](#):
> >
> > how would you route a Winbox connection through a socks proxy?
> 
> I assume that’s a rhetorical question.

Haha, actually no, just one based on an almost complete ignorance of socks!  
I did just find some interesting discussion here: [http://forum.mikrotik.com/t/winbox-socksv5-proxy/92658/1](http://forum.mikrotik.com/t/winbox-socksv5-proxy/92658/1)  
I think I now understand: I imagine he used an ssh client to open the socks connection then ssh to connect to his router through that tunnel.

---

_[View the full topic](https://forum.mikrotik.com/t/winbox-vulnerability-please-upgrade/122004)._
