{
    "file_item": {
        "filepath": "security-advisories",
        "filename": "CERT-EU-SA2020-049.pdf"
    },
    "title": "Critical Vulnerability in Microsoft Outlook",
    "serial_number": "2020-049",
    "publish_date": "14-10-2020 12:48:00",
    "description": "On 13th of October 2020, Microsoft released several security advisories to address security vulnerabilities. One of the reported vulnerabilities, affects Oulook, and it can be triggered by previewing a malicious e-mail. An attacker who successfully exploits this vulnerability could gain the ability to execute code on the target client.",
    "url_title": "2020-049",
    "content_markdown": "---\ntitle: 'Critical Vulnerability in\u00a0Microsoft\u00a0Outlook'\nversion: '1.0'\nnumber: '2020-049'\ndate: 'October 14, 2020'\n---\n\n_History:_\n\n* _14/10/2020 --- v1.0 -- Initial publication_\n\n# Summary\n\nOn 13th of October 2020, Microsoft released several security advisories to address security vulnerabilities. One of the reported vulnerabilities, affects Oulook, and it can be triggered by previewing a malicious e-mail. An attacker who successfully exploits this vulnerability could gain the ability to execute code on the target client [1].\n\n# Technical Details\n\nExploitation of the vulnerability requires that a user opens a specially crafted file with an affected version of Microsoft Outlook software. In an e-mail attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file designed to exploit the vulnerability. An attacker would have no way to force users to visit the website. Instead, an attacker would have to convince users to click a link, typically by way of an enticement in an e-mail or instant message, and then convince them to open the specially crafted file.\n\nThe remote code execution vulnerability exists in Microsoft Outlook software when the software fails to properly handle objects in memory. An attacker who successfully exploits the vulnerability could run arbitrary code in the context of the System user [1]. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights [1].\n\nThis vulnerability was reported through the ZDI program. The specific flaw exists within the parsing of HTML content in an email. The issue results from the lack of proper validation of the length of user-supplied data before copying it to a fixed-length heap-based buffer [2].\n\n# Affected Products\n\nMicrosoft Outlook 2016, Microsoft Outlook 2019 and Microsoft 365 Apps for Enterprise [1].\n\n# Recommendations\n\nApply the patches [1].\n\n## Mitigations\n\nMicrosoft has not identified any mitigating factors for this vulnerability.\n\n## Workarounds\n\nMicrosoft has not identified any workarounds for this vulnerability.\n\n# References\n\n[1] <https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-16947>\n\n[2] <https://www.zerodayinitiative.com/blog/2020/10/13/the-october-2020-security-update-review>\n",
    "content_html": "<p><em>History:</em></p><ul><li><em>14/10/2020 --- v1.0 -- Initial publication</em></li></ul><h2 id=\"summary\">Summary</h2><p>On 13th of October 2020, Microsoft released several security advisories to address security vulnerabilities. One of the reported vulnerabilities, affects Oulook, and it can be triggered by previewing a malicious e-mail. An attacker who successfully exploits this vulnerability could gain the ability to execute code on the target client [1].</p><h2 id=\"technical-details\">Technical Details</h2><p>Exploitation of the vulnerability requires that a user opens a specially crafted file with an affected version of Microsoft Outlook software. In an e-mail attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file designed to exploit the vulnerability. An attacker would have no way to force users to visit the website. Instead, an attacker would have to convince users to click a link, typically by way of an enticement in an e-mail or instant message, and then convince them to open the specially crafted file.</p><p>The remote code execution vulnerability exists in Microsoft Outlook software when the software fails to properly handle objects in memory. An attacker who successfully exploits the vulnerability could run arbitrary code in the context of the System user [1]. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights [1].</p><p>This vulnerability was reported through the ZDI program. The specific flaw exists within the parsing of HTML content in an email. The issue results from the lack of proper validation of the length of user-supplied data before copying it to a fixed-length heap-based buffer [2].</p><h2 id=\"affected-products\">Affected Products</h2><p>Microsoft Outlook 2016, Microsoft Outlook 2019 and Microsoft 365 Apps for Enterprise [1].</p><h2 id=\"recommendations\">Recommendations</h2><p>Apply the patches [1].</p><h3 id=\"mitigations\">Mitigations</h3><p>Microsoft has not identified any mitigating factors for this vulnerability.</p><h3 id=\"workarounds\">Workarounds</h3><p>Microsoft has not identified any workarounds for this vulnerability.</p><h2 id=\"references\">References</h2><p>[1] <a rel=\"noopener\" target=\"_blank\" href=\"https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-16947\">https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-16947</a></p><p>[2] <a rel=\"noopener\" target=\"_blank\" href=\"https://www.zerodayinitiative.com/blog/2020/10/13/the-october-2020-security-update-review\">https://www.zerodayinitiative.com/blog/2020/10/13/the-october-2020-security-update-review</a></p>",
    "licence": {
        "title": "Creative Commons Attribution 4.0 International (CC-BY 4.0)",
        "link": "https://creativecommons.org/licenses/by/4.0/",
        "restrictions": "https://cert.europa.eu/legal-notice",
        "author": "The Cybersecurity Service for the Union institutions, bodies, offices and agencies"
    }
}