Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

WanaCry Vulnerability

WanaCry Vulnerability

WanaCry Vulnerability

Anyone having to address the WanaCry vulnerability on CallPilot? We're patched current through Hotfix SECPEP018S. I see no recourse for correction on a CallPilot server short of unplugging from the CLAN. Anyone seen an official statement from Avaya?

RE: WanaCry Vulnerability

Haven't heard a statement from Avaya yet, but our network folks went ahead and patched our CP server (1005r at 5.51) and it crashed our server.

RE: WanaCry Vulnerability

Thanks SherWat. So they attempted to install the individual MS patch for Windows 2003 Server?

RE: WanaCry Vulnerability

Yes, I believe that is what they did.

RE: WanaCry Vulnerability

Has anyone done filtering or firewalling for 80/443 on the switch CLAN port to Call Pilot?

RE: WanaCry Vulnerability

So we have a big escalation on it, I have patched with KB4012598 on our Lab server and rebooted seems fine. I will be adding it to production servers tomorrow. I will come back if there are any issues, the patch from Microsoft wasn't put out until March so it would not be in SEC PEP 18. Like you say no mention on Avaya website for CP.

RE: WanaCry Vulnerability

I have also just installed the patch (KB4012598) on a lab 600r and it seems fine. We will patch the production servers tonight.

RE: WanaCry Vulnerability

Done production servers including ones with AACC with callpilot integration for IVR/ACCESS and working fine

RE: WanaCry Vulnerability

We have also patched all of our production servers including servers integrated with AACC and have had no issues. We were also instructed by our Data Security department to add a registry value of SMB1 and set it to disabled. The path for this value is:
Registry entry: SMB1
REG_DWORD: 0 = Disabled

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close