Microsoft Reveals Blockchain Tokens Platform

Microsoft Corporation’s (NASDAQ: MSFT) Azure Blockchain Tokens platform is now available for preview, the company announced on Monday.

What Happened

The new platform will allow enterprises or individuals to easily “create their own blockchain tokens” based on the Token Taxonomy Initiative (TTI) standards.

The TTI framework is essentially a “non-technical definition of what a token is,” decided upon by the members of the Enterprise Ethereum Alliance (EEA) which include Microsoft, JPMorgan Chase & Co. (NYSE: JPM), and ING Group N.V. (AMS: INGA), among other major companies and blockchain startups. IBM’s (NYSE: IBM) Hyperledger is also an associate member of the bloc.

What’s Next

Following the TTI framework will allow the tokens created on the Azure platform to have interoperability. It means that a token built on the Azure platform will be portable to, for example, IBM’s blockchain platform, as both of them run on the Ethereum network as of now.

“The industry has suffered from an IBM versus Microsoft thing, Hyperledger versus [Ethereum], and so on. We are trying to break down those barriers,” Microsoft’s Marley Grey, who also heads the EEA bloc, told CoinDesk.

“You can go and buy a printer or any type of device now and just plug it in, and it works. It’s the same analogy here for tokens, and that is what we are building in Azure,” he said.

Related:

Java removed during SEP client installation process?

I need a solution

My team and I are in the process of creating a uninstall/install package of our current AV(ESET) and install of SEP 14.2. We’ve noticed our uninstall/install package which includes Symantec’s third party AV remover + SEP Client 14.2 for Windows64bit also removes Java…other programs we’ve noticed that have been removed (winPcap, irfanview). 

We’ve narrowed it down to the third party AV remover as the culprite deleting Java but we’re not sure if this is configurable. We have memory exploit mitigration to log-only and have vanilla-out-of-the-box policies applied to the group the client installer sends new clients to. What’s also strange is that we have quarantines/blocks from Symantec to show notifications of actions but the removal of Java is completely silent and gets rid of the whole file directory. We’re in an environment with SAP and Java not being able to run is quite worrisome. 

Any advice/thoughts would be greatly appreciated. 

Log info: 

Mon Jul 16 17:26:02 2018 Unsupport Product: Vendor:Adobe Systems Inc., Name:Adobe Flash Player, Version:30.0.0.134, Product Category:WAAPI_CATEGORY_UNCLASSIFIED
Mon Jul 16 17:26:02 2018 Unsupport Product: Vendor:Microsoft Corporation, Name:Windows Update Agent, Version:10.0.17134.1, Product Category:WAAPI_CATEGORY_PATCH_MANAGEMENT
Mon Jul 16 17:26:02 2018 Unsupport Product: Vendor:Microsoft Corporation, Name:Windows VPN Client, Version:10.0.17134.1, Product Category:WAAPI_CATEGORY_VPN_CLIENT
Mon Jul 16 17:26:02 2018 Unsupport Product: Vendor:Microsoft Corporation, Name:Microsoft Publisher, Version:16.0.10228.20080, Product Category:WAAPI_CATEGORY_UNCLASSIFIED
Mon Jul 16 17:26:02 2018 Unsupport Product: Vendor:Microsoft Corporation, Name:Microsoft PowerPoint, Version:16.0.10228.20080, Product Category:WAAPI_CATEGORY_UNCLASSIFIED
Mon Jul 16 17:26:02 2018 Unsupport Product: Vendor:Microsoft Corporation, Name:Microsoft Outlook, Version:16.0.10228.20080, Product Category:WAAPI_CATEGORY_UNCLASSIFIED
Mon Jul 16 17:26:02 2018 Unsupport Product: Vendor:Microsoft Corporation, Name:Microsoft OneNote, Version:16.0.10228.20080, Product Category:WAAPI_CATEGORY_UNCLASSIFIED
Mon Jul 16 17:26:02 2018 Unsupport Product: Vendor:Microsoft Corporation, Name:Microsoft Excel, Version:16.0.10228.20080, Product Category:WAAPI_CATEGORY_UNCLASSIFIED
Mon Jul 16 17:26:02 2018 Unsupport Product: Vendor:Microsoft Corporation, Name:Microsoft Word, Version:16.0.10228.20080, Product Category:WAAPI_CATEGORY_UNCLASSIFIED
Mon Jul 16 17:26:25 2018 Success removed Product: Vendor:Oracle Corporation, Name:Java, Version:8.0.1710.11, Product Category:WAAPI_CATEGORY_UNCLASSIFIED

0

Related:

Microsoft Unveils The Coco Framework

On August 10, 2017, Microsoft Corporation (Microsoft) announced the Confidential Consortium (Coco) Framework, a blockchain protocol technology. The Coco Framework is not a blockchain itself and it is not tied to Azure, Microsoft’s cloud computing service.

Instead, Coco strives to provide the infrastructural foundation for blockchain networks. Using advanced algorithms and trusted execution environments (TEEs) – such as Intel Software Guard Extensions (SGX) or Windows Virtual Secure Mode (VSM) – the Coco Framework aims to meet the operational and security needs of enterprises. In early 2018, Microsoft plans to make Coco available on GitHub as an open source project.

“We expect this to be the foundation for blockchain for enterprise,” said Mark Russinovich, chief technology offer of Azure. Microsoft’s initial Coco Framework implementations include Ethereum (used in its prototype demonstration), R3 Corda, Intel’s Hyperledger Sawtooth, and JP Morgan’s Quorum.

According to the Coco Framework white paper, “enterprise-ready blockchains networks” will deliver many benefits including:

  • Throughput and latency approaching database speeds.
  • Richer, more flexible business-specific confidentiality models.
  • Network policy management through distributed governance.
  • Support for non-deterministic transactions.
  • Reduced energy consumption.

Microsoft boasts that Coco-enabled blockchain networks can achieve transactions speeds in excess of 1,600 transactions per second. The company also named Intel as “a key hardware and software development partner.”

Related:

Microsoft Security Advisory 3033929

Microsoft Security Advisory 3033929

Availability of SHA-2 Code Signing Support for Windows 7 and Windows Server 2008 R2

Published: March 10, 2015

Version: 1.0

On this page

General Information

Executive Summary

Microsoft is announcing the reissuance of an update for all supported editions of Windows 7 and Windows Server 2008 R2 to add support for SHA-2 signing and verification functionality. This update supersedes the 2949927 update that was rescinded on October 17, 2014 to address issues that some customers experienced after installation. As with the original release, Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows RT, and Windows RT 8.1 do not require this update because SHA-2 signing and verification functionality is already included in these operating systems. This update is not available for Windows Server 2003, Windows Vista, or Windows Server 2008.

Recommendation. Customers who have automatic updating enabled and configured to check online for updates from Microsoft Update typically will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For customers who install updates manually (including customers who have not enabled automatic updating), Microsoft recommends applying the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service. The updates are also available via the download links in the Affected Software table in this advisory.


Advisory Details

Issue References

For more information about this issue, see the following references:

References

Identification

Microsoft Knowledge Base Article

3033929  (supersedes 2949927) 


Affected Software

This advisory discusses the following software.

Operating System

Updates Replaced    

Windows 7 for 32-bit Systems Service Pack 1
(3033929)(1)

3035131 in MS15-025

Windows 7 for x64-based Systems Service Pack 1
(3033929)(1)

3035131 in MS15-025

Windows Server 2008 R2 for x64-based Systems Service Pack 1
(3033929)(1)

3035131 in MS15-025

Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
(3033929)(1)

3035131 in MS15-025

Server Core installation option

3035131 in MS15-025

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) (3033929)(1)

3035131 in MS15-025

[1]The 3033929 update has affected binaries in common with the 3035131 update being released simultaneously via MS15-025. Customers who download and install updates manually and who are planning to install both updates should install the 3035131 update before installing the 3033929 update. See the Advisory FAQ for more information.


Advisory FAQ

What is the scope of the advisory? The purpose of this advisory is to inform customers of an update that adds functionality for the SHA-2 hashing algorithm to all supported editions of Windows 7 and Windows Server 2008 R2.

Is this a security vulnerability that requires Microsoft to issue a security update? 
No. A signing mechanism alternative to SHA-1 has been available for some time, and the use of SHA-1 as a hashing algorithm for signing purposes has been discouraged and is no longer a best practice. Microsoft recommends using the SHA-2 hashing algorithm instead and is releasing this update to enable customers to migrate digital certificate keys to the more secure SHA-2 hashing algorithm.

What is the cause of the problem with the SHA-1 hashing algorithm? The root cause of the problem is a known weakness of the SHA-1 hashing algorithm that exposes it to collision attacks. Such attacks could allow an attacker to generate additional certificates that have the same digital signature as an original. These issues are well understood and the use of SHA-1 certificates for specific purposes that require resistance against these attacks has been discouraged. At Microsoft, the Security Development Lifecycle has required Microsoft to no longer use the SHA-1 hashing algorithm as a default functionality in Microsoft software. For more information, see Microsoft Security Advisory 2880823 and the Windows PKI blog entry, SHA1 Deprecation Policy.

What does the update do? The update adds SHA-2 hashing algorithm signing and verification support to affected operating systems, which includes the following:

What is Secure Hash Algorithm (SHA-1)? The Secure Hash Algorithm (SHA) was developed for use with the Digital Signature Algorithm (DSA) or the Digital Signature Standard (DSS) and generates a 160-bit hash value. SHA-1 has known weaknesses that exposes it to collision attacks. Such attacks could allow an attacker to generate additional certificates that have the same digital signature as an original. For more information about SHA-1, see Hash and Signature Algorithms.

What is RFC3161? 
RFC3161 defines the Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) describing the format of requests and responses to a Time Stamping Authority (TSA). The TSA is can be used to prove that a digital signature was generated during the validity period of a public key certificate, see X.509 Public Key Infrastructure.

What is a digital certificate? In public key cryptography, one of the keys, known as the private key, must be kept secret. The other key, known as the public key, is intended to be shared with the world. However, there must be a way for the owner of the key to tell the world to whom the key belongs. Digital certificates provide a way to do this. A digital certificate is an electronic credential used to certify the online identities of individuals, organizations, and computers. Digital certificates contain a public key packaged together with information about it (who owns it, what it can be used for, when it expires, and so forth). For more information, see Understanding Public Key Cryptography and Digital Certificates.

What is the purpose of a digital certificate? Digital certificates are used primarily to verify the identity of a person or device, authenticate a service, or encrypt files. Normally, there is no need to think about certificates at all, aside from the occasional message stating that a certificate is expired or invalid. In such cases, one should follow the instructions provided in the message.

How is this update (3033929) related to the 3035131 update discussed in MS15-025? This update (3033929) shares affected binaries with the 3035131 update being released simultaneously via MS15-025. This overlap necessitates that one update supersede the other and, in this case, advisory update 3033929 supersedes update 3035131. Customers with automatic updating enabled should experience no unusual installation behavior; both updates should install automatically and both should appear in the list of installed updates. However, for customers who download and install updates manually, the order in which the updates are installed will determine the observed behavior as follows:

Scenario 1 (preferred): Customer first installs update 3035131 and then installs advisory update 3033929. Result: Both updates should install normally and both updates should appear in the list of installed updates.  

Scenario 2: Customer first installs advisory update 3033929 and then attempts to install update 3035131.Result: The installer notifies the user that the 3035131 update is already installed on the system; and the 3035131 update is NOT added to the list of installed updates.


Suggested Actions

  • Apply the update for supported releases of Microsoft Windows

    The majority of customers have automatic updating enabled and will not need to take any action because the update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

    For administrators and enterprise installations, or end users who want to install this security update manually (including customers who have not enabled automatic updating), Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service. The updates are also available via the download links in the Affected Software table in this advisory.

Additional Suggested Actions

  • Protect your PC

    We continue to encourage customers to follow our Protect Your Computer guidance of enabling a firewall, getting software updates and installing antivirus software. For more information, see Microsoft Safety & Security Center.

  • Keep Microsoft Software Updated

    Users running Microsoft software should apply the latest Microsoft security updates to help make sure that their computers are as protected as possible. If you are not sure whether your software is up to date, visit Microsoft Update, scan your computer for available updates, and install any high-priority updates that are offered to you. If you have automatic updating enabled and configured to provide updates for Microsoft products, the updates are delivered to you when they are released, but you should verify that they are installed.


Other Information

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Feedback

Support

Disclaimer

The information provided in this advisory is provided “as is” without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions

  • V1.0 (March 10, 2015): Advisory published.

Page generated 2015-03-04 14:52Z-08:00.

Related:

Microsoft Security Bulletin MS15-014 – Important

Microsoft Security Bulletin MS15-014 – Important

Vulnerability in Group Policy Could Allow Security Feature Bypass (3004361)

Published: February 10, 2015

Version: 1.0

On this page


Executive Summary

This security update resolves a privately reported vulnerability in Microsoft Windows. The vulnerability could allow security feature bypass if an attacker, by way of a man-in-the-middle attack, causes the Group Policy Security Configuration Engine policy file on a targeted system to become corrupted or otherwise unreadable. This results in the Group Policy settings on the system to revert to their default, and potentially less secure, state.

This security update is rated Important for all supported releases of Microsoft Windows. For more information, see the Affected Software section.

The security update addresses the vulnerability by correcting how Group Policy settings are applied when the Security Configuration Engine policy file is corrupted or otherwise unreadable. For more information about the vulnerability, see the Vulnerability Information section.

For more information about this update, see Microsoft Knowledge Base Article 3004361.


Affected Software

The following software versions or editions are affected. Versions or editions that are not listed are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, see Microsoft Support Lifecycle.

Operating System

Maximum Security Impact

Aggregate Severity Rating

Updates Replaced

Windows Server 2003

Windows Server 2003 Service Pack 2 (3004361)

Security Feature Bypass

Important

None

Windows Server 2003 x64 Edition Service Pack 2 (3004361)

Security Feature Bypass

Important

None

Windows Server 2003 with SP2 for Itanium-based Systems (3004361)

Security Feature Bypass

Important

None

Windows Vista

Windows Vista Service Pack 2 (3004361)

Security Feature Bypass

Important

None

Windows Vista x64 Edition Service Pack 2 (3004361)

Security Feature Bypass

Important

None

Windows Server 2008

Windows Server 2008 for 32-bit Systems Service Pack 2 (3004361)

Security Feature Bypass

Important

None

Windows Server 2008 for x64-based Systems Service Pack 2 (3004361)

Security Feature Bypass

Important

None

Windows Server 2008 for Itanium-based Systems Service Pack 2 (3004361)

Security Feature Bypass

Important

None

Windows 7

Windows 7 for 32-bit Systems Service Pack 1 (3004361)

Security Feature Bypass

Important

None

Windows 7 for x64-based Systems Service Pack 1 (3004361)

Security Feature Bypass

Important

None

Windows Server 2008 R2

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (3004361)

Security Feature Bypass

Important

None

Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (3004361)

Security Feature Bypass

Important

None

Windows 8 and Windows 8.1

Windows 8 for 32-bit Systems (3004361)

Security Feature Bypass

Important

None

Windows 8 for x64-based Systems (3004361)

Security Feature Bypass

Important

None

Windows 8.1 for 32-bit Systems (3004361)

Security Feature Bypass

Important

None

Windows 8.1 for x64-based Systems (3004361)

Security Feature Bypass

Important

None

Windows Server 2012 and Windows Server 2012 R2

Windows Server 2012 (3004361)

Security Feature Bypass

Important

None

Windows Server 2012 R2 (3004361)

Security Feature Bypass

Important

None

Windows RT and Windows RT 8.1

Windows RT[1] (3004361)

Security Feature Bypass

Important

None

Windows RT 8.1[1] (3004361)

Security Feature Bypass

Important

None

Server Core installation option

Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)(3004361)

Security Feature Bypass

Important

None

Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) (3004361)

Security Feature Bypass

Important

None

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) (3004361)

Security Feature Bypass

Important

None

Windows Server 2012 (Server Core installation) (3004361)

Security Feature Bypass

Important

None

Windows Server 2012 R2 (Server Core installation) (3004361)

Security Feature Bypass

Important

None

[1]This update is available via Windows Update only.


Severity Ratings and Vulnerability Identifiers

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin’s release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the February bulletin summary.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software

Affected Software

Group Policy Security Feature Bypass Vulnerability – CVE-2015-0009

Aggregate Severity Rating

Windows Server 2003

Windows Server 2003 Service Pack 2 (3004361)

Important Security Feature Bypass

Important

Windows Server 2003 x64 Edition Service Pack 2 (3004361)

Important Security Feature Bypass

Important

Windows Server 2003 with SP2 for Itanium-based Systems (3004361)

Important Security Feature Bypass

Important

Windows Vista

Windows Vista Service Pack 2 (3004361)

Important Security Feature Bypass

Important

Windows Vista x64 Edition Service Pack 2 (3004361)

Important Security Feature Bypass

Important

Windows Server 2008

Windows Server 2008 for 32-bit Systems Service Pack 2 (3004361)

Important Security Feature Bypass

Important

Windows Server 2008 for x64-based Systems Service Pack 2 (3004361)

Important Security Feature Bypass

Important

Windows Server 2008 for Itanium-based Systems Service Pack 2 (3004361)

Important Security Feature Bypass

Important

Windows 7

Windows 7 for 32-bit Systems Service Pack 1 (3004361)

Important Security Feature Bypass

Important

Windows 7 for x64-based Systems Service Pack 1 (3004361)

Important Security Feature Bypass

Important

Windows Server 2008 R2

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (3004361)

Important Security Feature Bypass

Important

Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (3004361)

Important Security Feature Bypass

Important

Windows 8 and Windows 8.1

Windows 8 for 32-bit Systems (3004361)

Important Security Feature Bypass

Important

Windows 8 for x64-based Systems (3004361)

Important Security Feature Bypass

Important

Windows 8.1 for 32-bit Systems (3004361)

Important Security Feature Bypass

Important

Windows 8.1 for x64-based Systems (3004361)

Important Security Feature Bypass

Important

Windows Server 2012 and Windows Server 2012 R2

Windows Server 2012 (3004361)

Important Security Feature Bypass

Important

Windows Server 2012 R2 (3004361)

Important Security Feature Bypass

Important

Windows RT and Windows RT 8.1

Windows RT[1] (3004361)

Important Security Feature Bypass

Important

Windows RT 8.1[1] (3004361)

Important Security Feature Bypass

Important

Server Core installation option

Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)(3004361)

Important Security Feature Bypass

Important

Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) (3004361)

Important Security Feature Bypass

Important

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) (3004361)

Important Security Feature Bypass

Important

Windows Server 2012 (Server Core installation) (3004361)

Important Security Feature Bypass

Important

Windows Server 2012 R2 (Server Core installation) (3004361)

Important Security Feature Bypass

Important


Vulnerability Information

Group Policy Security Feature Bypass Vulnerability – CVE-2015-0009

A security feature bypass vulnerability exists in the Group Policy application of Security Configuration policies that could cause Group Policy settings on a targeted system to revert to their default, and potentially less secure, state. An attacker could accomplish this by way of a man-in-the-middle attack that modifies domain controller responses to client requests.

Workstations and servers that are configured to use Group Policy are primarily at risk from this vulnerability. The update addresses the vulnerability by correcting how Group Policy settings are applied when the Security Configuration Engine policy file is corrupted or otherwise unreadable.

Microsoft received information about this vulnerability through coordinated vulnerability disclosure. When this security bulletin was originally issued Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers.

Mitigating Factors

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds

Microsoft has not identified any workarounds for this vulnerability.


Security Update Deployment

For Security Update Deployment information, see the Microsoft Knowledge Base article referenced here in the Executive Summary.


Acknowledgments

Microsoft recognizes the efforts of those in the security community who help us protect customers through responsible vulnerability disclosure. See Acknowledgments for more information.


Disclaimer

The information provided in the Microsoft Knowledge Base is provided “as is” without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.


Revisions

  • V1.0 (February 10, 2015): Bulletin published.

Page generated 2015-02-04 14:13Z-08:00.

Related:

Microsoft Security Bulletin MS14-080 – Critical

Microsoft Security Bulletin MS14-080 – Critical

Cumulative Security Update for Internet Explorer (3008923)

Published: December 9, 2014 | Updated: April 14, 2015

Version: 3.0

On this page


Executive Summary

This security update resolves fourteen privately reported vulnerabilities in Internet Explorer. The most severe of these vulnerabilities could allow remote code execution if a user views a specially crafted webpage using Internet Explorer. An attacker who successfully exploited these vulnerabilities could gain the same user rights as the current user. Customers whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

This security update is rated Critical for Internet Explorer 6 (IE 6), Internet Explorer 7 (IE 7), Internet Explorer 8 (IE 8), Internet Explorer 9 (IE 9), Internet Explorer 10 (IE 10), and Internet Explorer 11 (IE 11) on affected Windows clients, and Moderate for Internet Explorer 6 (IE 6), Internet Explorer 7 (IE 7), Internet Explorer 8 (IE 8), Internet Explorer 9 (IE 9), Internet Explorer 10 (IE 10), and Internet Explorer 11 (IE 11) on affected Windows servers. For more information, see the Affected Software section.

The security update addresses the vulnerabilities by modifying the way that Internet Explorer handles objects in memory, by preventing the XSS filter in Internet Explorer from incorrectly disabling HTML attributes, by helping to ensure that affected versions of Internet Explorer properly implement the ASLR security feature, and by modifying how the VBScript scripting engine handles objects in memory. For more information about the vulnerabilities, see the Vulnerability Information section.

For more information about this update, see Microsoft Knowledge Base Article 3008923.

 


Affected Software

The following software versions or editions are affected. Versions or editions that are not listed are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, see Microsoft Support Lifecycle.

Affected Software 

Operating System

Component

Maximum Security Impact

Aggregate Severity Rating

Updates Replaced

Internet Explorer 6

Windows Server 2003 Service Pack 2

Internet Explorer 6 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2003 x64 Edition Service Pack 2

Internet Explorer 6 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2003 with SP2 for Itanium-based Systems

Internet Explorer 6 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Internet Explorer 7

Windows Server 2003 Service Pack 2

Internet Explorer 7 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2003 x64 Edition Service Pack 2

Internet Explorer 7 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2003 with SP2 for Itanium-based Systems

Internet Explorer 7 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Vista Service Pack 2

Internet Explorer 7 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Vista x64 Edition Service Pack 2

Internet Explorer 7 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Server 2008 for 32-bit Systems Service Pack 2

Internet Explorer 7 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2008 for x64-based Systems Service Pack 2

Internet Explorer 7 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2008 for Itanium-based Systems Service Pack 2

Internet Explorer 7 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Internet Explorer 8

Windows Server 2003 Service Pack 2

Internet Explorer 8 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2003 x64 Edition Service Pack 2

Internet Explorer 8 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Vista Service Pack 2

Internet Explorer 8 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Vista x64 Edition Service Pack 2

Internet Explorer 8 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Server 2008 for 32-bit Systems Service Pack 2

Internet Explorer 8 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2008 for x64-based Systems Service Pack 2

Internet Explorer 8 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows 7 for 32-bit Systems Service Pack 1

Internet Explorer 8 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows 7 for x64-based Systems Service Pack 1

Internet Explorer 8 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Server 2008 R2 for x64-based Systems Service Pack 1

Internet Explorer 8 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2008 R2 for Itanium-based Systems Service Pack 1

Internet Explorer 8 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Internet Explorer 9

Windows Vista Service Pack 2

Internet Explorer 9 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Vista x64 Edition Service Pack 2

Internet Explorer 9 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Server 2008 for 32-bit Systems Service Pack 2

Internet Explorer 9 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2008 for x64-based Systems Service Pack 2

Internet Explorer 9 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows 7 for 32-bit Systems Service Pack 1

Internet Explorer 9 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows 7 for x64-based Systems Service Pack 1

Internet Explorer 9 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Server 2008 R2 for x64-based Systems Service Pack 1

Internet Explorer 9 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Internet Explorer 10

Windows 7 for 32-bit Systems Service Pack 1

Internet Explorer 10 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows 7 for x64-based Systems Service Pack 1

Internet Explorer 10 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Server 2008 R2 for x64-based Systems Service Pack 1

Internet Explorer 10 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows 8 for 32-bit Systems

Internet Explorer 10 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows 8 for 32-bit Systems

Internet Explorer 10 (3029449)[1]

Remote Code Execution

Critical

None

Windows 8 for x64-based Systems

Internet Explorer 10 (3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows 8 for x64-based Systems

Internet Explorer 10 (3029449)[1]

Remote Code Execution

Critical

None

Windows Server 2012

Internet Explorer 10 (3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows Server 2012

Internet Explorer 10 (3029449)[1]

Remote Code Execution

Moderate

None

Windows RT

Internet Explorer 10[2](3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows RT

Internet Explorer 10[2](3029449)[1]

Remote Code Execution

Critical

None

Internet Explorer 11

Windows 7 for 32-bit Systems Service Pack 1

Internet Explorer 11
(3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows 7 for x64-based Systems Service Pack 1

Internet Explorer 11
(3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Server 2008 R2 for x64-based Systems Service Pack 1

Internet Explorer 11
(3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows 8.1 for 32-bit Systems

Internet Explorer 11
(3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows 8.1 for x64-based Systems

Internet Explorer 11
(3008923)

Remote Code Execution

Critical

3003057 in MS14-065

Windows Server 2012 R2

Internet Explorer 11
(3008923)

Remote Code Execution

Moderate

3003057 in MS14-065

Windows RT 8.1

Internet Explorer 11[2](3008923)

Remote Code Execution

Critical

3003057 in MS14-065

[1]Customers running Internet Explorer 10 on Windows 8, Windows Server 2012, or Window RT should install both updates (3008923 and 3029449).

[2]This update is available via Windows Update.

Note For systems running Internet Explorer 9 or later, CVE-2014-6363 is addressed by this update (3008923). For all other affected versions of Internet Explorer, CVE-2014-6363 is addressed by the update described in MS14-084. For more information, see the Update FAQ.

Note Windows Technical Preview and Windows Server Technical Preview are affected. Customers running these operating systems are encouraged to apply the update, which is available via Windows Update. 


Update FAQ

For addressing CVE-2014-6363, what update applies to my system? CVE-2014-6363 is a vulnerability in the VBScript scripting engine. Although the attack vector is through Internet Explorer, this vulnerability is addressed by this update (3008923) only for systems running Internet Explorer 9, Internet Explorer 10, and Internet Explorer 11. For Internet Explorer 8 and earlier and for systems without Internet Explorer installed, this vulnerability is addressed by the update described in MS14-084.

The update that addresses CVE-2014-6363 depends on the version of the VBScript scripting engine that is installed on your system. Consult the following table for update information.

Version

MS14-084

MS14-080

VBScript 5.6(Internet Explorer 6)

VBScript 5.6 (3012168)

Not applicable

VBScript 5.7(Internet Explorer 6 and Internet Explorer 7)

VBScript 5.7 (3012172)

Not applicable

VBScript 5.8(Internet Explorer 8)

VBScript 5.8 (3012176)

Not applicable

VBScript 5.8(Internet Explorer 9)

Not applicable

Internet Explorer 9 (3008923)

VBScript 5.8(Internet Explorer 10)

Not applicable

Internet Explorer 10 (3008923)

VBScript 5.8(Internet Explorer 11)

Not applicable

Internet Explorer 11 (3008923)


Severity Ratings and Vulnerability Identifiers

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin’s release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the December bulletin summary.

In the following table Where specified, Critical, Important, and Moderate values indicate severity ratings. For more information, see Security Bulletin Severity Rating System. Where specified, the abbreviations as shown in the following key indicate maximum impact:

Abbreviation

Maximum Impact

RCE

Remote Code Execution

EoP

Elevation of Privilege

ID

Information Disclosure

SFB

Security Feature Bypass

 

Severity Ratings and Impact

CVE number

Vulnerability Title

Internet Explorer 6

Internet Explorer 7

Internet Explorer 8

Internet Explorer 9

Internet Explorer 10

Internet Explorer 11

CVE-2014-6327

Internet Explorer Memory Corruption Vulnerability

Not applicable

Not applicable

Not applicable

Not applicable

Not applicable

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

CVE-2014-6328

Internet Explorer XSS Filter Bypass Vulnerability

Not applicable

Not applicable

Windows Clients: Important / SFBWindows Servers: Low / SFB

Windows Clients: Important / SFBWindows Servers: Low / SFB

Windows Clients: Important / SFBWindows Servers: Low / SFB

Windows Clients: Important / SFBWindows Servers: Low / SFB

CVE-2014-6329

Internet Explorer Memory Corruption Vulnerability

Not applicable

Not applicable

Not applicable

Not applicable

Not applicable

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

CVE-2014-6330

Internet Explorer Memory Corruption Vulnerability

Not applicable

Not applicable

Not applicable

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Not applicable

Not applicable

CVE-2014-6363

VBScript Memory Corruption Vulnerability

Not applicable

Not applicable

Not applicable

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

CVE-2014-6365

Internet Explorer XSS Filter Bypass Vulnerability

Not applicable

Not applicable

Windows Clients: Important / SFBWindows Servers: Low / SFB

Windows Clients: Important / SFBWindows Servers: Low / SFB

Windows Clients: Important / SFBWindows Servers: Low / SFB

Windows Clients: Important / SFBWindows Servers: Low / SFB

CVE-2014-6366

Internet Explorer Memory Corruption Vulnerability

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Not applicable

Not applicable

Not applicable

Not applicable

CVE-2014-6368

Internet Explorer ASLR Bypass Vulnerability

Not applicable

Not applicable

Not applicable

Not applicable

Not applicable

Windows Clients: Important / SFBWindows Servers: Low / SFB

CVE-2014-6369

Internet Explorer Memory Corruption Vulnerability

Not applicable

Not applicable

Not applicable

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

CVE-2014-6373

Internet Explorer Memory Corruption Vulnerability

Not applicable

Not applicable

Not applicable

Not applicable

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Not applicable

CVE number

Vulnerability Title

Internet Explorer 6

Internet Explorer 7

Internet Explorer 8

Internet Explorer 9

Internet Explorer 10

Internet Explorer 11

CVE-2014-6374

Internet Explorer Memory Corruption Vulnerability

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

CVE-2014-6375

Internet Explorer Memory Corruption Vulnerability

Not applicable

Not applicable

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Not applicable

Not applicable

Not applicable

CVE-2014-6376

Internet Explorer Memory Corruption Vulnerability

Not applicable

Not applicable

Not applicable

Not applicable

Not applicable

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

CVE-2014-8966

Internet Explorer Memory Corruption Vulnerability

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Windows Clients: Critical / RCEWindows Servers: Moderate / RCE

Not applicable

Not applicable

Not applicable

 


Vulnerability Information

Multiple Memory Corruption Vulnerabilities in Internet Explorer

Remote code execution vulnerabilities exist when Internet Explorer improperly accesses objects in memory. These vulnerabilities could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. The update addresses the vulnerabilities by modifying the way that Internet Explorer handles objects in memory.

An attacker could host a specially crafted website that is designed to exploit these vulnerabilities through Internet Explorer, and then convince a user to view the website. The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements by adding specially crafted content that could exploit these vulnerabilities. In all cases, however, an attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically by getting them to click a link in an email message or in an Instant Messenger message that takes users to the attacker’s website, or by getting them to open an attachment sent through email.

An attacker who successfully exploited these vulnerabilities could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited these vulnerabilities could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from these vulnerabilities.

The update addresses the vulnerabilities by modifying the way that Internet Explorer handles objects in memory.

The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:

Vulnerability title

CVE number

Publicly Disclosed

Exploited

Internet Explorer Memory Corruption Vulnerability

CVE-2014-6327

No

No

Internet Explorer Memory Corruption Vulnerability

CVE-2014-6329

No

No

Internet Explorer Memory Corruption Vulnerability

CVE-2014-6330

No

No

Internet Explorer Memory Corruption Vulnerability

CVE-2014-6366

No

No

Internet Explorer Memory Corruption Vulnerability

CVE-2014-6369

No

No

Internet Explorer Memory Corruption Vulnerability

CVE-2014-6373

No

No

Internet Explorer Memory Corruption Vulnerability

CVE-2014-6374

No

No

Internet Explorer Memory Corruption Vulnerability

CVE-2014-6375

No

No

Internet Explorer Memory Corruption Vulnerability

CVE-2014-6376

No

No

Internet Explorer Memory Corruption Vulnerability

CVE-2014-8966

No

No

Mitigating Factors

Microsoft has not identified any mitigating factors for these vulnerabilities.

Workarounds

Microsoft has not identified any workarounds for these vulnerabilities.

FAQ

I am running Internet Explorer on Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2. Does this mitigate these vulnerabilities? Yes. By default, Internet Explorer on Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted web content on a server. This is a mitigating factor for websites that you have not added to the Internet Explorer Trusted sites zone.

Does EMET help mitigate attacks that could attempt to exploit these vulnerabilities? Yes. The Enhanced Mitigation Experience Toolkit (EMET) enables users to manage security mitigation technologies that help make it more difficult for attackers to exploit vulnerabilities in a given piece of software. EMET helps to mitigate these vulnerabilities in Internet Explorer on systems where EMET is installed and configured to work with Internet Explorer.

For more information about EMET, see The Enhanced Mitigation Experience Toolkit.

Multiple XSS Filter Bypass Vulnerabilities in Internet Explorer

XSS filter bypass vulnerabilities exist in the way that Internet Explorer disables an HTML attribute in otherwise appropriately filtered HTTP response data. The vulnerabilities could allow initially disabled scripts to run in the wrong security context, leading to information disclosure.

An attacker could post on a website specially crafted content that is designed to exploit this vulnerability. The attacker would then have to convince the user to view the content on the affected website. If the user then browses to the website, the XSS filter disables HTML attributes in the specially crafted content, creating a condition that could allow malicious script to run in the wrong security context, leading to information disclosure.

An attacker who successfully exploited this vulnerability could cause script code to run on another user’s system in the guise of a third-party website. Such script code would run inside the browser when visiting the third-party website, and could take any action on the user’s system that the third-party website was permitted to take. The vulnerability could only be exploited if the user clicked on a hypertext link, either in an HTML email or if the user visited an attacker’s website or a website containing content that is under the attacker’s control. Any systems where Internet Explorer is used frequently, such as workstations and terminal servers, are at the most risk from this vulnerability.

The update addresses the vulnerability by preventing the XSS filter in Internet Explorer from incorrectly disabling HTML attributes.

The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:

Vulnerability title

CVE number

Publicly Disclosed

Exploited

Internet Explorer XSS Filter Bypass Vulnerability

CVE-2014-6328

No

No

Internet Explorer XSS Filter Bypass Vulnerability

CVE-2014-6365

No

No

Mitigating Factors

Microsoft has not identified any mitigating factors for these vulnerabilities.

Workarounds

Microsoft has not identified any workarounds for these vulnerabilities.

Internet Explorer ASLR Bypass Vulnerability – CVE-2014-6368

A security feature bypass vulnerability exists when Internet Explorer does not use the Address Space Layout Randomization (ASLR) security feature, allowing an attacker to more reliably predict the memory offsets of specific instructions in a given call stack. An attacker who successfully exploited this vulnerability could bypass the Address Space Layout Randomization (ASLR) security feature, which helps protect users from a broad class of vulnerabilities. The security feature bypass by itself does not allow arbitrary code execution. However, an attacker could use this ASLR bypass vulnerability in conjunction with another vulnerability, such as a remote code execution vulnerability, that could take advantage of the ASLR bypass to run arbitrary code. For example, a remote code execution vulnerability that is blocked by ASLR, could be exploited after a successful ASLR bypass.

In a web-browsing scenario, successful exploitation of this vulnerability requires that a user is logged on and running an affected version of Internet Explorer. Therefore, any systems where a web browser is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability. Servers could be at more risk if administrators allow users to browse and read email on servers. However, best practices strongly discourage allowing this.

The update addresses the vulnerability by helping to ensure that affected versions of Internet Explorer properly implement the ASLR security feature.

The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:

Vulnerability title

CVE number

Publicly Disclosed

Exploited

Internet Explorer ASLR Bypass Vulnerability

CVE-2014-6368

No

No

Mitigating Factors

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds

Microsoft has not identified any workarounds for this vulnerability.

VBScript Memory Corruption Vulnerability – CVE-2014-6363

A remote code execution vulnerability exists in the way that the VBScript engine, when rendered in Internet Explorer, handles objects in memory. The vulnerability may corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user.

An attacker could host a specially crafted website that is designed to exploit this vulnerability through Internet Explorer and then convince a user to view the website. An attacker could also embed an ActiveX control marked “safe for initialization” in an application or Microsoft Office document that hosts the IE rendering engine. The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements by adding specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically by getting them to click a link in an email message or in an Instant Messenger message that takes users to the attacker’s website, or by opening an attachment sent through email.

An attacker who successfully exploited this vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Systems on which Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.

The update addresses the vulnerability by modifying how the VBScript scripting engine handles objects in memory.

The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:

Vulnerability title

CVE number

Publicly Disclosed

Exploited

VBScript Memory Corruption Vulnerability

CVE-2014-6363

No

No

Mitigating Factors

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds

Microsoft has not identified any workarounds for this vulnerability.

FAQ

I am running Internet Explorer for Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2. Does this mitigate this vulnerability? Yes. By default, Internet Explorer on Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted web content on a server. This is a mitigating factor for websites that you have not added to the Internet Explorer Trusted sites zone.


Security Update Deployment

For Security Update Deployment information see the Microsoft Knowledge Base article referenced here in the Executive Summary.


Acknowledgments

Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgments for more information.


Disclaimer

The information provided in the Microsoft Knowledge Base is provided “as is” without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.


Revisions

Page generated 2015-04-09 15:17Z-07:00.

Related: