Re: [cisco-voip] Cisco Voice Operating System-Based Products Unauthorized Access Vulnerability

[Erick Bergquist]

Looking at doing the same, pushing the cop file.

"file search install system-history.log Upgrade"  will show just the
Upgrade entries. Can look to see if a nornal upgrade was done after a
refresh entry.


On Wed, Nov 22, 2017 at 8:08 AM, Brian Meade  wrote:
> We've got a team doing some scripting to check the system-history.log.  It
> looks like there is no harm to running the COP on a non-affected system as
> well so we may just push it in bulk.
>
> On Wed, Nov 22, 2017 at 9:01 AM, Ryan Ratliff (rratliff)
>  wrote:
>>
>> I’d rather you take the approach of telling all of your customers to
>> install the COP file rather than pen-testing on a live system :)
>>
>> If you want to see if they are exposed get the system-history.log and
>> install.log and upload them to a TAC SR or manually inspect them to
>> determine the timeline of install & upgrade types. All the info you need is
>> in the advisory.
>> PCD Migration -> exposed
>> RU Upgrade -> exposed
>> L2 Upgrade -> not exposed
>>
>> -Ryan
>>
>> On Nov 20, 2017, at 11:25 AM, Brian Meade  wrote:
>>
>> Anyone got some ideas on trying to crack this UCOS password?  Should help
>> us out in scanning our customers to see if they are affected, but we
>> wouldn't want this password to end up indexed by google and make the issue
>> even worse.
>>
>> On Fri, Nov 17, 2017 at 4:46 PM, Anthony Holloway
>>  wrote:
>>>
>>> Bwahaha! I just logged in to your CUCM Tim.
>>>
>>> On a serious note, I think it’s interesting how this “flag” issue is such
>>> a big deal, when back in the old days of UCCX, Cisco was creating an
>>> intentional back-door in all installs, using the same username and password
>>> on all of them.
>>>
>>> For the curious, it was :
>>>
>>> Username: CRSAdministrator
>>> Password: NwY.t9g(f'L9[3C
>>>
>>> If you have access to a UCCX 7x or lower, try logging in to Windows with
>>> that account and report back if it worked.
>>>
>>> If it does work, check the MADM logs on the C: for the clear text AXL
>>> username and password, so you can compromise CUCM too!
>>> On Fri, Nov 17, 2017 at 1:46 PM Tim Frazee  wrote:

 heads up


 https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171115-vos


 ___
 cisco-voip mailing list
 cisco-voip@puck.nether.net
 https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>> ___
>>> cisco-voip mailing list
>>> cisco-voip@puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Cisco Voice Operating System-Based Products Unauthorized Access Vulnerability

[Brian Meade]

We've got a team doing some scripting to check the system-history.log.  It
looks like there is no harm to running the COP on a non-affected system as
well so we may just push it in bulk.

On Wed, Nov 22, 2017 at 9:01 AM, Ryan Ratliff (rratliff)  wrote:

> I’d rather you take the approach of telling all of your customers to
> install the COP file rather than pen-testing on a live system :)
>
> If you want to see if they are exposed get the system-history.log and
> install.log and upload them to a TAC SR or manually inspect them to
> determine the timeline of install & upgrade types. All the info you need is
> in the advisory.
> PCD Migration -> exposed
> RU Upgrade -> exposed
> L2 Upgrade -> not exposed
>
> -Ryan
>
> On Nov 20, 2017, at 11:25 AM, Brian Meade  wrote:
>
> Anyone got some ideas on trying to crack this UCOS password?  Should help
> us out in scanning our customers to see if they are affected, but we
> wouldn't want this password to end up indexed by google and make the issue
> even worse.
>
> On Fri, Nov 17, 2017 at 4:46 PM, Anthony Holloway <
> avholloway+cisco-v...@gmail.com> wrote:
>
>> Bwahaha! I just logged in to your CUCM Tim.
>>
>> On a serious note, I think it’s interesting how this “flag” issue is such
>> a big deal, when back in the old days of UCCX, Cisco was creating an
>> intentional back-door in all installs, using the same username and password
>> on all of them.
>>
>> For the curious, it was :
>>
>> Username: CRSAdministrator
>> Password: NwY.t9g(f'L9[3C
>>
>> If you have access to a UCCX 7x or lower, try logging in to Windows with
>> that account and report back if it worked.
>>
>> If it does work, check the MADM logs on the C: for the clear text AXL
>> username and password, so you can compromise CUCM too!
>> On Fri, Nov 17, 2017 at 1:46 PM Tim Frazee  wrote:
>>
>>> heads up
>>>
>>> https://tools.cisco.com/security/center/content/CiscoSecurit
>>> yAdvisory/cisco-sa-20171115-vos
>>>
>>>
>>> ___
>>> cisco-voip mailing list
>>> cisco-voip@puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Cisco Voice Operating System-Based Products Unauthorized Access Vulnerability

[Ryan Ratliff (rratliff)]

I’d rather you take the approach of telling all of your customers to install 
the COP file rather than pen-testing on a live system :)

If you want to see if they are exposed get the system-history.log and 
install.log and upload them to a TAC SR or manually inspect them to determine 
the timeline of install & upgrade types. All the info you need is in the 
advisory.
PCD Migration -> exposed
RU Upgrade -> exposed
L2 Upgrade -> not exposed

-Ryan

On Nov 20, 2017, at 11:25 AM, Brian Meade 
> wrote:

Anyone got some ideas on trying to crack this UCOS password?  Should help us 
out in scanning our customers to see if they are affected, but we wouldn't want 
this password to end up indexed by google and make the issue even worse.

On Fri, Nov 17, 2017 at 4:46 PM, Anthony Holloway 
> wrote:
Bwahaha! I just logged in to your CUCM Tim.

On a serious note, I think it’s interesting how this “flag” issue is such a big 
deal, when back in the old days of UCCX, Cisco was creating an intentional 
back-door in all installs, using the same username and password on all of them.

For the curious, it was :

Username: CRSAdministrator
Password: NwY.t9g(f'L9[3C

If you have access to a UCCX 7x or lower, try logging in to Windows with that 
account and report back if it worked.

If it does work, check the MADM logs on the C: for the clear text AXL username 
and password, so you can compromise CUCM too!
On Fri, Nov 17, 2017 at 1:46 PM Tim Frazee 
> wrote:
heads up

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171115-vos


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Cisco Voice Operating System-Based Products Unauthorized Access Vulnerability

[Pete Brown]

If you have an affected lab box, any chance you could package up few files and 
send them over off list?



From: bmead...@gmail.com <bmead...@gmail.com> on behalf of Brian Meade 
<bmead...@vt.edu>
Sent: Monday, November 20, 2017 11:48 AM
To: Pete Brown
Cc: Anthony Holloway; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Cisco Voice Operating System-Based Products 
Unauthorized Access Vulnerability

I was thinking about running John the Ripper on a lab box that is affected to 
try to get the password.  Not sure if it will find anything though.

On Mon, Nov 20, 2017 at 11:50 AM, Pete Brown 
<j...@chykn.com<mailto:j...@chykn.com>> wrote:

I wonder if there are any existing penetration testing utilities to check for 
these conditions on UCOS hosts?


If not, challenge accepted.


From: cisco-voip 
<cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net>> 
on behalf of Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>>
Sent: Monday, November 20, 2017 10:25 AM
To: Anthony Holloway
Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Cisco Voice Operating System-Based Products 
Unauthorized Access Vulnerability

Anyone got some ideas on trying to crack this UCOS password?  Should help us 
out in scanning our customers to see if they are affected, but we wouldn't want 
this password to end up indexed by google and make the issue even worse.

On Fri, Nov 17, 2017 at 4:46 PM, Anthony Holloway 
<avholloway+cisco-v...@gmail.com<mailto:avholloway+cisco-v...@gmail.com>> wrote:
Bwahaha! I just logged in to your CUCM Tim.

On a serious note, I think it’s interesting how this “flag” issue is such a big 
deal, when back in the old days of UCCX, Cisco was creating an intentional 
back-door in all installs, using the same username and password on all of them.

For the curious, it was :

Username: CRSAdministrator
Password: NwY.t9g(f'L9[3C

If you have access to a UCCX 7x or lower, try logging in to Windows with that 
account and report back if it worked.

If it does work, check the MADM logs on the C: for the clear text AXL username 
and password, so you can compromise CUCM too!
On Fri, Nov 17, 2017 at 1:46 PM Tim Frazee 
<tfra...@gmail.com<mailto:tfra...@gmail.com>> wrote:
heads up

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171115-vos<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.cisco.com%2Fsecurity%2Fcenter%2Fcontent%2FCiscoSecurityAdvisory%2Fcisco-sa-20171115-vos=02%7C01%7Cjpb%40chykn.com%7Cc6d62618f1394047c79708d530335cb9%7C84df9e7fe9f640afb435%7C1%7C0%7C636467919512806356=IdvnVpdKRKohCUKQSKKh4bKfelSJUiZAdjH11YhCLns%3D=0>


___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip=02%7C01%7Cjpb%40chykn.com%7Cc6d62618f1394047c79708d530335cb9%7C84df9e7fe9f640afb435%7C1%7C0%7C636467919512806356=vOKtR8Wsv5fwFmwmyehk7Nn8m7NSLCh4DhqdDBz5Bos%3D=0>

___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip=02%7C01%7Cjpb%40chykn.com%7Cc6d62618f1394047c79708d530335cb9%7C84df9e7fe9f640afb435%7C1%7C0%7C636467919512806356=vOKtR8Wsv5fwFmwmyehk7Nn8m7NSLCh4DhqdDBz5Bos%3D=0>



___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Cisco Voice Operating System-Based Products Unauthorized Access Vulnerability

[Brian Meade]

I was thinking about running John the Ripper on a lab box that is affected
to try to get the password.  Not sure if it will find anything though.

On Mon, Nov 20, 2017 at 11:50 AM, Pete Brown <j...@chykn.com> wrote:

> I wonder if there are any existing penetration testing utilities to check
> for these conditions on UCOS hosts?
>
>
> If not, challenge accepted.
>
> --
> *From:* cisco-voip <cisco-voip-boun...@puck.nether.net> on behalf of
> Brian Meade <bmead...@vt.edu>
> *Sent:* Monday, November 20, 2017 10:25 AM
> *To:* Anthony Holloway
> *Cc:* cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] Cisco Voice Operating System-Based Products
> Unauthorized Access Vulnerability
>
> Anyone got some ideas on trying to crack this UCOS password?  Should help
> us out in scanning our customers to see if they are affected, but we
> wouldn't want this password to end up indexed by google and make the issue
> even worse.
>
> On Fri, Nov 17, 2017 at 4:46 PM, Anthony Holloway <
> avholloway+cisco-v...@gmail.com> wrote:
>
> Bwahaha! I just logged in to your CUCM Tim.
>
> On a serious note, I think it’s interesting how this “flag” issue is such
> a big deal, when back in the old days of UCCX, Cisco was creating an
> intentional back-door in all installs, using the same username and password
> on all of them.
>
> For the curious, it was :
>
> Username: CRSAdministrator
> Password: NwY.t9g(f'L9[3C
>
> If you have access to a UCCX 7x or lower, try logging in to Windows with
> that account and report back if it worked.
>
> If it does work, check the MADM logs on the C: for the clear text AXL
> username and password, so you can compromise CUCM too!
> On Fri, Nov 17, 2017 at 1:46 PM Tim Frazee <tfra...@gmail.com> wrote:
>
> heads up
>
> https://tools.cisco.com/security/center/content/CiscoSecurit
> yAdvisory/cisco-sa-20171115-vos
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.cisco.com%2Fsecurity%2Fcenter%2Fcontent%2FCiscoSecurityAdvisory%2Fcisco-sa-20171115-vos=02%7C01%7Cjpb%40chykn.com%7Cc6d62618f1394047c79708d530335cb9%7C84df9e7fe9f640afb435%7C1%7C0%7C636467919512806356=IdvnVpdKRKohCUKQSKKh4bKfelSJUiZAdjH11YhCLns%3D=0>
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip=02%7C01%7Cjpb%40chykn.com%7Cc6d62618f1394047c79708d530335cb9%7C84df9e7fe9f640afb435%7C1%7C0%7C636467919512806356=vOKtR8Wsv5fwFmwmyehk7Nn8m7NSLCh4DhqdDBz5Bos%3D=0>
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip=02%7C01%7Cjpb%40chykn.com%7Cc6d62618f1394047c79708d530335cb9%7C84df9e7fe9f640afb435%7C1%7C0%7C636467919512806356=vOKtR8Wsv5fwFmwmyehk7Nn8m7NSLCh4DhqdDBz5Bos%3D=0>
>
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Cisco Voice Operating System-Based Products Unauthorized Access Vulnerability

[Pete Brown]

I wonder if there are any existing penetration testing utilities to check for 
these conditions on UCOS hosts?


If not, challenge accepted.


From: cisco-voip <cisco-voip-boun...@puck.nether.net> on behalf of Brian Meade 
<bmead...@vt.edu>
Sent: Monday, November 20, 2017 10:25 AM
To: Anthony Holloway
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Cisco Voice Operating System-Based Products 
Unauthorized Access Vulnerability

Anyone got some ideas on trying to crack this UCOS password?  Should help us 
out in scanning our customers to see if they are affected, but we wouldn't want 
this password to end up indexed by google and make the issue even worse.

On Fri, Nov 17, 2017 at 4:46 PM, Anthony Holloway 
<avholloway+cisco-v...@gmail.com<mailto:avholloway+cisco-v...@gmail.com>> wrote:
Bwahaha! I just logged in to your CUCM Tim.

On a serious note, I think it’s interesting how this “flag” issue is such a big 
deal, when back in the old days of UCCX, Cisco was creating an intentional 
back-door in all installs, using the same username and password on all of them.

For the curious, it was :

Username: CRSAdministrator
Password: NwY.t9g(f'L9[3C

If you have access to a UCCX 7x or lower, try logging in to Windows with that 
account and report back if it worked.

If it does work, check the MADM logs on the C: for the clear text AXL username 
and password, so you can compromise CUCM too!
On Fri, Nov 17, 2017 at 1:46 PM Tim Frazee 
<tfra...@gmail.com<mailto:tfra...@gmail.com>> wrote:
heads up

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171115-vos<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.cisco.com%2Fsecurity%2Fcenter%2Fcontent%2FCiscoSecurityAdvisory%2Fcisco-sa-20171115-vos=02%7C01%7Cjpb%40chykn.com%7Cc6d62618f1394047c79708d530335cb9%7C84df9e7fe9f640afb435%7C1%7C0%7C636467919512806356=IdvnVpdKRKohCUKQSKKh4bKfelSJUiZAdjH11YhCLns%3D=0>


___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip=02%7C01%7Cjpb%40chykn.com%7Cc6d62618f1394047c79708d530335cb9%7C84df9e7fe9f640afb435%7C1%7C0%7C636467919512806356=vOKtR8Wsv5fwFmwmyehk7Nn8m7NSLCh4DhqdDBz5Bos%3D=0>

___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip=02%7C01%7Cjpb%40chykn.com%7Cc6d62618f1394047c79708d530335cb9%7C84df9e7fe9f640afb435%7C1%7C0%7C636467919512806356=vOKtR8Wsv5fwFmwmyehk7Nn8m7NSLCh4DhqdDBz5Bos%3D=0>


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Cisco Voice Operating System-Based Products Unauthorized Access Vulnerability

[Brian Meade]

Anyone got some ideas on trying to crack this UCOS password?  Should help
us out in scanning our customers to see if they are affected, but we
wouldn't want this password to end up indexed by google and make the issue
even worse.

On Fri, Nov 17, 2017 at 4:46 PM, Anthony Holloway <
avholloway+cisco-v...@gmail.com> wrote:

> Bwahaha! I just logged in to your CUCM Tim.
>
> On a serious note, I think it’s interesting how this “flag” issue is such
> a big deal, when back in the old days of UCCX, Cisco was creating an
> intentional back-door in all installs, using the same username and password
> on all of them.
>
> For the curious, it was :
>
> Username: CRSAdministrator
> Password: NwY.t9g(f'L9[3C
>
> If you have access to a UCCX 7x or lower, try logging in to Windows with
> that account and report back if it worked.
>
> If it does work, check the MADM logs on the C: for the clear text AXL
> username and password, so you can compromise CUCM too!
> On Fri, Nov 17, 2017 at 1:46 PM Tim Frazee  wrote:
>
>> heads up
>>
>> https://tools.cisco.com/security/center/content/
>> CiscoSecurityAdvisory/cisco-sa-20171115-vos
>>
>>
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Cisco Voice Operating System-Based Products Unauthorized Access Vulnerability

[Charles Goldsmith]

Indeed it works, and sadly, I have a customer with uccx 7 still running...

On Fri, Nov 17, 2017 at 3:46 PM, Anthony Holloway <
avholloway+cisco-v...@gmail.com> wrote:

> Bwahaha! I just logged in to your CUCM Tim.
>
> On a serious note, I think it’s interesting how this “flag” issue is such
> a big deal, when back in the old days of UCCX, Cisco was creating an
> intentional back-door in all installs, using the same username and password
> on all of them.
>
> For the curious, it was :
>
> Username: CRSAdministrator
> Password: NwY.t9g(f'L9[3C
>
> If you have access to a UCCX 7x or lower, try logging in to Windows with
> that account and report back if it worked.
>
> If it does work, check the MADM logs on the C: for the clear text AXL
> username and password, so you can compromise CUCM too!
> On Fri, Nov 17, 2017 at 1:46 PM Tim Frazee  wrote:
>
>> heads up
>>
>> https://tools.cisco.com/security/center/content/
>> CiscoSecurityAdvisory/cisco-sa-20171115-vos
>>
>>
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Cisco Voice Operating System-Based Products Unauthorized Access Vulnerability

[Anthony Holloway]

Bwahaha! I just logged in to your CUCM Tim.

On a serious note, I think it’s interesting how this “flag” issue is such a
big deal, when back in the old days of UCCX, Cisco was creating an
intentional back-door in all installs, using the same username and password
on all of them.

For the curious, it was :

Username: CRSAdministrator
Password: NwY.t9g(f'L9[3C

If you have access to a UCCX 7x or lower, try logging in to Windows with
that account and report back if it worked.

If it does work, check the MADM logs on the C: for the clear text AXL
username and password, so you can compromise CUCM too!
On Fri, Nov 17, 2017 at 1:46 PM Tim Frazee  wrote:

> heads up
>
>
> https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171115-vos
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] Cisco Voice Operating System-Based Products Unauthorized Access Vulnerability

[Tim Frazee]

heads up

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171115-vos
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip