Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of
Robert Hass
>I'm looking for exploitation of issue 'Cisco IOS-XE 3S platforms Series
Root Shell License Bypass Vulnerability' (CSCuv93130). I would like to check
if it's really working on my Ciscos >r
Pavel,
I am still not convinced...
Can you please share your config and maybe a sniffer trace on the client?
Tnx, Arie
On Sat, Feb 27, 2016, 23:27 Pavel Dimow wrote:
> Hi Arie,
>
> no, that's not the case since I use local policy routing to force traffic
> to go via correct provider and I can
On 28 February 2016 at 04:18, Robert Hass wrote:
Hey,
> I'm looking for exploitation of issue 'Cisco IOS-XE 3S platforms Series
> Root Shell License Bypass Vulnerability' (CSCuv93130). I would like to
> check if it's really working on my Ciscos running IOS XE. Anyone have
> recipe how to do it ?
On Sat, 27 Feb 2016, James Bensley wrote:
Erase the box, push up the new image and original config. That way the
network state is known at all times without having to ask the PEs.
Everything is nice and consistent.
This is a workaround because the vendor did a shoddy job with package and
con
On 28/Feb/16 12:45, James Bensley wrote:
> Doh! Miss read your email!
>
> Out of curiosity, what takes you to 15.5 over 15.3 or 15.4 (15.4 seems too
> buggy to me, but I'm happy with 15.3(3)S4/5/6 as long as there aren't
> features you need missing from there) - was it features or bugs or both?
On 27 Feb 2016 16:07, "Mark Tinka" wrote:
>
>
>
> On 27/Feb/16 17:54, James Bensley wrote:
>
> > If you're going to the trouble, push on to 15.3(3)S6, it's only
> > additional bug fixes no added features.
>
> 15.5S and 15.3S are separate trains.
>
> I'm on the 15.5S train.
>
> Mark.
Doh! Miss rea
