Category: Information Security
Please do not respond to a recent message that appears to come from the IT Help Center (email@example.com) with the Subject “IMPORTANT NOTICE.” Although this message contains BU logos and a sender address that make it seem legitimate, it is a phishing message. To learn more, especially if you did already respond to the message or click on the link it provides, please contact the Service Desk at 617-638-5914 or refer to the page on Spoofed Messages and Phishing.
As always, if you are unsure whether an e-mail is real or if you receive an e-mail message that is abusive or harassing in nature, report it to firstname.lastname@example.org. If possible, it is helpful to include full headers when forwarding a message.
(View the original post from IS&T here)
Action Required for all Microsoft Windows Users:
- If you are running Microsoft Windows and you do not have it set to Automatically Update, you should run Windows Update immediately. See instructions at www.bu.edu/tech/desktop/virus-protection-security/safe-computing/autoupdate/ and confirm that you have the correct patches using the instructions below on this page.
- If you do have Automatic Updates turned on, you should have received the patch last Tuesday and you are all set – no further action is required toward installing it. You can confirm that you are updating automatically by following the instructions at www.bu.edu/tech/desktop/virus-protection-security/safe-computing/autoupdate/.
- If you use Microsoft Windows Remote Desktop (RDP) to connect to a BU computer from outside of BU, you will need to connect to the VPN prior to connecting via RDP – login at http://vpn.bu.edu.
- If you have set up your system to allow remote access, or if you run a server, see the additional instructions below.
On Tuesday, March 13, Microsoft announced that a critical vulnerability had been discovered in all versions of Windows from XP and up. This vulnerability affects the Remote Desktop (RDP) feature of Windows. RDP allows a remote user to connect to the computer and the vulnerability may allow even an unauthorized person to do so.
An exploit has already been released that will cause a Blue Screen of Death on Windows 7 and a Denial of Service on Windows XP. It is expected that another exploit will soon be released that will allow an attacker to have complete control of the computer. After that, the next expected step is that a self-replicating worm will be released that will automatically jump from host to host, granting the attacker access to the system and taking any other action the attacker may wish.
Microsoft has released a patch for this vulnerability. See below for details on installing it.
What IS&T and the IT Partners are doing:
- IS&T and the IT Partners have been working to install this patch on the servers at BU.
- Due to the serious nature of this vulnerability, IS&T will be blocking RDP access at the BU firewall within the next few days. This block is necessary because it is common for people to disable the automatic update functionality. It can reasonably be expected that many systems will remain unpatched for an extended period of time. If we take no action to block access to RDP through the firewall, exploit code could significantly impact the stable operation of computers at BU or otherwise compromise BU operations or protected information. (For reference, as of Monday (3/19) there were over 3000 computers at BU that had RDP up and operating.)
If you never use RDP…:
- If you do not need to use RDP, you can disable it. Instructions are provided below.
- If you do need to use RDP, please follow the security best practices published by IS&T:
Best practices include moving RDP away from its standard port to some other port protected by the BU Edge Firewall.
If you are running a server:
- Patch information can be found here: http://technet.microsoft.com/en-us/security/bulletin/ms12-020
- If the system cannot be immediately patched, please see this page for an alternative “fix it” option:http://blogs.technet.com/b/srd/archive/2012/03/13/cve-2012-0002-a-closer-look-at-ms12-020-s-critical-issue.aspx
Confirm that you have the correct patches:
1. Go to Start -> All Programs -> Windows Update -> View Update History and confirm that KB2667402 and KB2621440 are installed
- Go to Start -> Microsoft Update -> Review your update history
- Confirm that KB2621440 is installed
How to disable RDP if you don’t use it:
- Go to Control Panel, click System And Security, and then click System.
- On the System page, click Remote Settings in the left pane. This opens the System Properties dialog box to theRemote tab.
- To disable Remote Desktop, select Don’t Allow Connections To This Computer,
- Also uncheck the Allow Remote Assistance box as shown below and then click OK
- Click System in Control Panel.
- On the Remote tab, clear the Allow users to connect remotely to your computer check box, and then click OK.
Last week, Symantec said it was unable to predict when it would complete its patching of pcAnywhere, citing the unpredictability of its investigation and the creation of the necessary fixes. However, they have now released an update that addresses the security issues we reported earlier this week. We therefore will not be implementing an inbound filter to 5631/TCP, 5632/UDP on Sunday 2/5 as previously mentioned.
The updates can be manually downloaded from Symantec’s website, or customers can use pcAnywhere’s built-in updating service to retrieve and install the patches. http://www.symantec.com/business/support/index?page=content&id=TECH179960
Modena also confirmed that customers running versions of pcAnywhere prior to version 12.0 will be offered a free upgrade to 12.5. “If requested, Symantec will honor an update to version 12.5 for the customer.”
Information Security Incident Response Team, Information Services & Technology
Security Alert – Due to a security issue with pcAnywhere, we plan to create a new rule to block in bound traffic to ports: 5631/TCP, 5632/UDP. This rule will go into effect on Sunday, 2/5.
If you are using pcAnywhere, please read this message in its entirety.
In a white paper released on 1/23, Symantec revealed that proprietary source code for current versions of its pcAnywhere software were stolen in 2006 and that all users are at risk of attack and should disable the product.
Symantec, in their official report on this event, provides this statement: “Symantec recommends disabling the product until Symantec releases a final set of software updates that resolve currently known vulnerability risks.“
What you should do:
- For any system that contains Restricted Use information, pcAnywhere must be disabled and alternatives sought. (For a definition of Restricted Use information, please see the Data Classification Guide, part of the Data Protection Standards: http://www.bu.edu/infosec/policies/data-protection-standards/)
- For any other system where you are using pcAnywhere and where an alternative solution will work, you should switch to the alternate solutions. Some possible solutions include:
- Windows Remote Desktop (see http://www.bu.edu/tech/security/protect/bestpractice/remote-desktop/ for details)
- GotomyPC (security has not evaluated this product and it does have a price tag, so this is not a specific recommendation of this product, but simply an alternative if Remote Desktop will not work)
- Avoid RealVNC. It is known to have significant security issues.
- Where you (1) have a business critical function (2) on a system not containing Restricted Use information and (3) pcAnywhere is the only solution that will work for that function, you may continue to use it provided you do the following:
- Upgrade to the latest version
- Update your pcAnywhere configuration as recommended in the white paper from Symantec in the “pcAnywhere Security Best Practices” section, beginning on page 5
- Set up your pcAnywhere connection to use different authentication credentials than you use for any other BU system
- If you are outside of BU, Connect to BU via VPN prior to establishing the pcAnywhere connection
- Monitor Symantec’s site for further security information and updates
What we will be doing:
- As recommended by the vendor, we will be writing a new rule to block traffic coming in to BU using the standard pcAnywhere communication ports: 5631/TCP, 5632/UDP. This rule will go into effect on Sunday, 2/5.
Sun Java 6.0.24
As announced in a notification from IBM, Host On-Demand is not supported by Java 6, update 24 and will not work after the computer has been upgraded. If you have upgraded to the most recent version of Java, we recommend downgrading to update 23:
Sun Java 6.0.21
When using Java 6 update 21, you will receive a security notification when trying to connect with Host On-Demand.
To remove this warning, named HODAPPlet:
- Open your Control Panel.
- Click on the Java icon.
- Select the Advanced tab.
- Choose Security.
- For “Mixed code (sandboxed vs trusted) security verification,” choose Hide warning and run with protections.
Sun Java 6.0.15, 6.0.16, and 6.0.17
If you are using either Sun Java 6.0 update 15, 16, or 17, Host On-Demand will not install or start in any browser.
As a work around, the next-generation plug-in can be disabled in the Java control panel.
- Open the Java control panel (Start/Control Panel/Java).
- Select the Advanced tab.
- Select Java plug-in.
- Uncheck Enable the next-generation Java plug-in.
- Click OK.
- A confirmation dialog box will appear. Click OK.
- Restart HOD.
Internet Explorer 8
If you are using IE 8, Host On-Demand may not install or start, depending on the version of Sun Java that is installed.
As a workaround, revert back to Sun Java 6.0.14.
- Uninstall Java 6.0.15 (or any more recent version, if installed)
- Download Java 6.0.14.
- Double-click on the 6.0.14 file to install.
- Re-install Host On-Demand.
Note: Administrative privileges are required.
If you got an e-mail from “email@example.com” asking you to supply for you email username and email password appears to be a phishing scheme. We would *never* ask you to e-mail your password. Please just delete the e-mail.
As always, if you have an e-mail that is suspect, you can call the Service Desk at (617) 638-5419 or forward the e-mail to firstname.lastname@example.org to verify if it is legitimate.
For more information about phishing e-mails, click here.
Many at BUMC are victims of “spamming” attacks and are forced to filter through hundreds of unwanted and inappropriate email daily. While there’s no cure for spam, BUMC IT encourages using SpamAssassin for anyone with a BU email account to minimize its effects. Questions? Contact (617) 638-5914 or email@example.com.
Click here for more information about Information Security.