[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3DsqEWoL3qpbeExMrI18k_LO0YQYkGN8Vo8Cb7UWyWE":3},{"id":4,"question":5,"answer":6,"answerHtml":7,"slug":8,"keywords":9,"article":10,"status":33,"aiModel":38,"aiConfidence":38,"updatedAt":50,"createdAt":50,"_status":49},1225,"What are the two main methods for detecting the version of a Microsoft Exchange server?","The two methods are accessing the EWS interface to get the exact build number from the `X-OWA-Version` response header, and accessing the OWA interface to parse an approximate version from the HTML content. The exact method is preferred for precision, but if it fails, the approximate method provides a usable version range. For more details, see [Penetration Basics - Exchange Version Detection and Vulnerability Scanning](\u002Fnews\u002Fpenetration-basics-exchange-version-detection-and-vulnerability-scanning). Similar version detection techniques can be applied to other services like [Minio](\u002Fnews\u002Fpenetration-basics-minio-version-detection-1) or [Zimbra](\u002Fnews\u002Fpenetration-basics-zimbra-version-detection1).","\u003Cp>The two methods are accessing the EWS interface to get the exact build number from the `X-OWA-Version` response header, and accessing the OWA interface to parse an approximate version from the HTML content. The exact method is preferred for precision, but if it fails, the approximate method provides a usable version range. For more details, see [Penetration Basics - Exchange Version Detection and Vulnerability Scanning](\u002Fnews\u002Fpenetration-basics-exchange-version-detection-and-vulnerability-scanning). Similar version detection techniques can be applied to other services like [Minio](\u002Fnews\u002Fpenetration-basics-minio-version-detection-1) or [Zimbra](\u002Fnews\u002Fpenetration-basics-zimbra-version-detection1).\u003C\u002Fp>\u003Cp>\u003Ca href=\"\u002Fnews\u002Fpenetration-basics-exchange-version-detection-and-vulnerability-scanning\">Read the related One Day Sec article\u003C\u002Fa>\u003C\u002Fp>","what-are-the-two-main-methods-for-detecting-the-version-of-a-microsoft-exchange--1777480018532","Exchange, version detection, EWS, OWA, build number, approximate version",{"id":11,"title":12,"slug":13,"description":14,"content":15,"contentHtml":30,"cover":31,"author":32,"views":19,"readingTime":31,"status":33,"publishedAt":34,"seo":35,"tags":40,"qaPairs":41,"meta":46,"updatedAt":47,"createdAt":48,"_status":49},295,"Penetration Basics - Exchange Version Detection and Vulnerability Scanning","penetration-basics-exchange-version-detection-and-vulnerability-scanning","Learn Python methods for Exchange version detection and vulnerability scanning. Includes code for EWS\u002FOWA interfaces and patch-based vulnerability assessment.",{"root":16},{"type":17,"format":18,"indent":19,"version":20,"children":21,"direction":29},"root","",0,1,[22],{"type":23,"format":18,"indent":19,"version":20,"children":24,"direction":29},"paragraph",[25],{"mode":26,"text":27,"type":28,"style":18,"detail":19,"format":19,"version":20},"normal","\u003Chtml>\u003Chead>\u003C\u002Fhead>\u003Cbody>\u003Ch2>0x00 Preface\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Cp>Exchange has numerous versions and a large number of historical vulnerabilities, making it necessary to implement version detection and vulnerability scanning through programs. This article will introduce two methods for version detection using Python, detail the implementation of vulnerability scanning, and provide open-source code.\u003C\u002Fp>\u003Ch2>0x01 Introduction\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Cp>This article will cover the following:\u003C\u002Fp>\u003Cul>\u003Cli>Implementation Approach\u003C\u002Fli>\u003Cli>Implementation Details\u003C\u002Fli>\u003Cli>Open-Source Code\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>0x02 Implementation Approach\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Ch3>1. Version Identification\u003C\u002Fh3>\u003Ch4>(1) Obtain the Exact Version (Build Number)\u003C\u002Fh4>\u003Cp>Access the EWS interface; the exact version can be obtained from the X-OWA-Version in the Response Headers, as shown in the figure below\u003C\u002Fp>\u003Cp>\u003Cimg alt=\"Alt text\" src=\"\u002Fuploads\u002Fdocx_image_1770016710705_0_4ca3c0fb11.jpeg\">\u003C\u002Fp>\u003Cp>Advantage: Precise version (Build number) can correspond to specific release dates\u003C\u002Fp>\u003Cp>Disadvantage: The method is not universal; some older Exchange versions are not supported\u003C\u002Fp>\u003Ch4>(2) Obtain approximate version\u003C\u002Fh4>\u003Cp>Access the OWA interface; the approximate version can be obtained from the echoed content, as shown in the figure below\u003C\u002Fp>\u003Cp>\u003Cimg alt=\"Alt text\" src=\"\u002Fuploads\u002Fdocx_image_1770016715981_1_2ad92565ee.jpeg\">\u003C\u002Fp>\u003Cp>Advantage: The method is universal\u003C\u002Fp>\u003Cp>Disadvantage: The approximate version cannot correspond to an exact release date, only to a range\u003C\u002Fp>\u003Cp>In summary, for version identification, first attempt to obtain the precise version; if that fails, then attempt to obtain the approximate version\u003C\u002Fp>\u003Cp>After obtaining the version number, you can query the corresponding Exchange version and release date on the official website. Query address: https:\u002F\u002Fdocs.microsoft.com\u002Fen-us\u002Fexchange\u002Fnew-features\u002Fbuild-numbers-and-release-dates?view=exchserver-2019\u003C\u002Fp>\u003Ch3>2. Vulnerability Detection\u003C\u002Fh3>\u003Cp>Details of Exchange vulnerabilities can be viewed by accessing https:\u002F\u002Fmsrc.microsoft.com\u002Fupdate-guide\u002Fvulnerability\u002F\u003Ccve>, for example:\u003C\u002Fcve>\u003C\u002Fp>\u003Cp>URL for CVE-2020-0688: https:\u002F\u002Fmsrc.microsoft.com\u002Fupdate-guide\u002Fvulnerability\u002FCVE-2020-0688\u003C\u002Fp>\u003Cp>For vulnerability detection, the patch date can be used as a criterion. If the identified Exchange version's release date is earlier than a certain patch date, then it is determined that the Exchange is vulnerable to the vulnerability described in that patch.\u003C\u002Fp>\u003Ch2>0x03 Implementation Details\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Ch3>1. Version Identification\u003C\u002Fh3>\u003Cp>Implementation code for obtaining version by accessing EWS interface:\u003C\u002Fp>\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd>\u003Cp>url1 = \"https:\u002F\u002F\" + host + \"\u002Fews\"\u003Cbr>req = requests.get(url1, headers = headers, verify=False)\u003Cbr>if \"X-OWA-Version\" in req.headers:\u003Cbr>    version = req.headers[\"X-OWA-Version\"]\u003Cbr>    print(version)\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Cp>Implementation code for obtaining version by accessing OWA interface:\u003C\u002Fp>\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd>\u003Cp>url2 = \"https:\u002F\u002F\" + host + \"\u002Fowa\"\u003Cbr>req = requests.get(url2, headers = headers, verify=False)\u003Cbr>pattern_version = re.compile(r\"\u002Fowa\u002Fauth\u002F(.*?)\u002Fthemes\u002Fresources\u002Ffavicon.ico\")\u003Cbr>version = pattern_version.findall(req.text)[0]\u003Cbr>print(version)\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Cp>After obtaining the version number, it needs to be matched against known version information. To improve efficiency, you can choose to store known version information in a list, with elements including Exchange version, release date, and build number\u003C\u002Fp>\u003Cp>First, copy known version information from the official website, then store the version information in a list via string replacement.\u003C\u002Fp>\u003Cp>During version matching, it is necessary to distinguish between exact versions and approximate versions. Exact versions can correspond to a unique result, while approximate versions require filtering out all possible results.\u003C\u002Fp>\u003Cp>Build number format example: 15.1.2375.24\u003C\u002Fp>\u003Cp>Approximate version format example: 15.1.2375\u003C\u002Fp>\u003Cp>Approximate version filtering method:\u003C\u002Fp>\u003Cp>Truncate the Build number string by removing the data after the last character \".\", then compare it with the approximate version and output all results.\u003C\u002Fp>\u003Cp>Code example:\u003C\u002Fp>\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd>\u003Cp>versionarray = [\u003Cbr>[\"Exchange Server 2019 CU11 Mar22SU\", \"March 8, 2022\", \"15.2.986.22\"],\u003Cbr>[\"Exchange Server 2019 CU11 Jan22SU\", \"January 11, 2022\", \"15.2.986.15\"],\u003Cbr>[\"Exchange Server 2019 CU11 Nov21SU\", \"November 9, 2021\", \"15.2.986.14\"],\u003Cbr>[\"Exchange Server 2019 CU11 Oct21SU\", \"October 12, 2021\", \"15.2.986.9\"],\u003Cbr>[\"Exchange Server 2019 CU11\", \"September 28, 2021\", \"15.2.986.5\"],\u003Cbr>[\"Exchange Server 2019 CU10 Mar22SU\", \"March 8, 2022\", \"15.2.922.27\"]\u003Cbr>]\u003Cbr>version=\"15.2.986\"\u003Cbr>for value in versionarray:\u003Cbr>    if version in value[2][:value[2].rfind(\".\")]:\u003Cbr>        print(\"[+] Version: \" + value[2])\u003Cbr>        print(\"    Product: \" + value[0])\u003Cbr>        print(\"    Date: \" + value[1])\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch3>2. Vulnerability Detection\u003C\u002Fh3>\u003Cp>Using patch time as the basis for judgment, and similarly to improve efficiency, storing known vulnerability information in a list, with elements including release date and vulnerability number\u003C\u002Fp>\u003Cp>To facilitate time comparison, it is necessary to change the time format, for example, modifying September 28, 2021 to 09\u002F28\u002F2021\u003C\u002Fp>\u003Cp>Code example:\u003C\u002Fp>\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd>\u003Cp>vularray = [\u003Cbr>[\"CVE-2020-0688\", \"02\u002F11\u002F2020\"],\u003Cbr>[\"CVE-2021-26855+CVE-2021-27065\", \"03\u002F02\u002F2021\"],\u003Cbr>[\"CVE-2021-28482\", \"04\u002F13\u002F2021\"]\u003Cbr>]\u003Cbr>date=\"03\u002F01\u002F2021\"\u003Cbr>for value in vularray:\u003Cbr>    if (date.split('\u002F')[2] < value[1].split('\u002F')[2]):\u003Cbr>        print(\"[+] \" + value[0] + \", \" + value[1])\u003Cbr>    else:\u003Cbr>        if (date.split('\u002F')[2] == value[1].split('\u002F')[2]) & (date.split('\u002F')[0] < value[1].split('\u002F')[0]):\u003Cbr>            print(\"[+] \" + value[0] + \", \" + value[1])\u003Cbr>        else:\u003Cbr>            if (date.split('\u002F')[2] == value[1].split('\u002F')[2]) & (date.split('\u002F')[0] == value[1].split('\u002F')[0]) & (date.split('\u002F')[1] < value[1].split('\u002F')[1]):\u003Cbr>                print(\"[+] \" + value[0] + \", \" + value[1])\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch2>0x04 Open Source Code\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Cp>Due to the length of the code content, the complete implementation code has been uploaded to GitHub at the following address:\u003C\u002Fp>\u003Cp>An open-source project\u003C\u002Fp>\u003Cp>The version database date is 03\u002F21\u002F2022\u003C\u002Fp>\u003Cp>Vulnerability information includes the following identifiers:\u003C\u002Fp>\u003Cul>\u003Cli>CVE-2020-0688\u003C\u002Fli>\u003Cli>CVE-2021-26855+CVE-2021-27065\u003C\u002Fli>\u003Cli>CVE-2021-28482\u003C\u002Fli>\u003Cli>CVE-2021-34473+CVE-2021-34523+CVE-2021-31207\u003C\u002Fli>\u003Cli>CVE-2021-31195+CVE-2021-31196\u003C\u002Fli>\u003Cli>CVE-2021-31206\u003C\u002Fli>\u003Cli>CVE-2021-42321\u003C\u002Fli>\u003C\u002Ful>\u003Cp>The code can automatically identify the exact version; if identification fails, it switches to identifying the approximate version and marks all matching vulnerabilities.\u003C\u002Fp>\u003Ch2>0x05 Summary\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Cp>This article introduces two methods for Exchange version detection using Python, detailing their implementation, providing open-source code, and serving as an excellent learning example.\u003C\u002Fp>\u003C\u002Fbody>\u003C\u002Fhtml>","text","ltr","\u003Chtml>\u003Chead>\u003C\u002Fhead>\u003Cbody>\u003Ch2>0x00 Preface\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Cp>Exchange has numerous versions and a large number of historical vulnerabilities, making it necessary to implement version detection and vulnerability scanning through programs. This article will introduce two methods for version detection using Python, detail the implementation of vulnerability scanning, and provide open-source code.\u003C\u002Fp>\u003Ch2>0x01 Introduction\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Cp>This article will cover the following:\u003C\u002Fp>\u003Cul>\u003Cli>Implementation Approach\u003C\u002Fli>\u003Cli>Implementation Details\u003C\u002Fli>\u003Cli>Open-Source Code\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>0x02 Implementation Approach\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Ch3>1. Version Identification\u003C\u002Fh3>\u003Ch4>(1) Obtain the Exact Version (Build Number)\u003C\u002Fh4>\u003Cp>Access the EWS interface; the exact version can be obtained from the X-OWA-Version in the Response Headers, as shown in the figure below\u003C\u002Fp>\u003Cp>\u003Cimg alt=\"Alt text\" src=\"\u002Fapi\u002Fmedia\u002Ffile\u002Fdocx_image_1770016710705_0_4ca3c0fb11-1.jpeg\">\u003C\u002Fp>\u003Cp>Advantage: Precise version (Build number) can correspond to specific release dates\u003C\u002Fp>\u003Cp>Disadvantage: The method is not universal; some older Exchange versions are not supported\u003C\u002Fp>\u003Ch4>(2) Obtain approximate version\u003C\u002Fh4>\u003Cp>Access the OWA interface; the approximate version can be obtained from the echoed content, as shown in the figure below\u003C\u002Fp>\u003Cp>\u003Cimg alt=\"Alt text\" src=\"\u002Fapi\u002Fmedia\u002Ffile\u002Fdocx_image_1770016715981_1_2ad92565ee-1.jpeg\">\u003C\u002Fp>\u003Cp>Advantage: The method is universal\u003C\u002Fp>\u003Cp>Disadvantage: The approximate version cannot correspond to an exact release date, only to a range\u003C\u002Fp>\u003Cp>In summary, for version identification, first attempt to obtain the precise version; if that fails, then attempt to obtain the approximate version\u003C\u002Fp>\u003Cp>After obtaining the version number, you can query the corresponding Exchange version and release date on the official website. Query address: https:\u002F\u002Fdocs.microsoft.com\u002Fen-us\u002Fexchange\u002Fnew-features\u002Fbuild-numbers-and-release-dates?view=exchserver-2019\u003C\u002Fp>\u003Ch3>2. Vulnerability Detection\u003C\u002Fh3>\u003Cp>Details of Exchange vulnerabilities can be viewed by accessing https:\u002F\u002Fmsrc.microsoft.com\u002Fupdate-guide\u002Fvulnerability\u002F\u003Ccve>, for example:\u003C\u002Fcve>\u003C\u002Fp>\u003Cp>URL for CVE-2020-0688: https:\u002F\u002Fmsrc.microsoft.com\u002Fupdate-guide\u002Fvulnerability\u002FCVE-2020-0688\u003C\u002Fp>\u003Cp>For vulnerability detection, the patch date can be used as a criterion. If the identified Exchange version's release date is earlier than a certain patch date, then it is determined that the Exchange is vulnerable to the vulnerability described in that patch.\u003C\u002Fp>\u003Ch2>0x03 Implementation Details\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Ch3>1. Version Identification\u003C\u002Fh3>\u003Cp>Implementation code for obtaining version by accessing EWS interface:\u003C\u002Fp>\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd>\u003Cp>url1 = \"https:\u002F\u002F\" + host + \"\u002Fews\"\u003Cbr>req = requests.get(url1, headers = headers, verify=False)\u003Cbr>if \"X-OWA-Version\" in req.headers:\u003Cbr>    version = req.headers[\"X-OWA-Version\"]\u003Cbr>    print(version)\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Cp>Implementation code for obtaining version by accessing OWA interface:\u003C\u002Fp>\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd>\u003Cp>url2 = \"https:\u002F\u002F\" + host + \"\u002Fowa\"\u003Cbr>req = requests.get(url2, headers = headers, verify=False)\u003Cbr>pattern_version = re.compile(r\"\u002Fowa\u002Fauth\u002F(.*?)\u002Fthemes\u002Fresources\u002Ffavicon.ico\")\u003Cbr>version = pattern_version.findall(req.text)[0]\u003Cbr>print(version)\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Cp>After obtaining the version number, it needs to be matched against known version information. To improve efficiency, you can choose to store known version information in a list, with elements including Exchange version, release date, and build number\u003C\u002Fp>\u003Cp>First, copy known version information from the official website, then store the version information in a list via string replacement.\u003C\u002Fp>\u003Cp>During version matching, it is necessary to distinguish between exact versions and approximate versions. Exact versions can correspond to a unique result, while approximate versions require filtering out all possible results.\u003C\u002Fp>\u003Cp>Build number format example: 15.1.2375.24\u003C\u002Fp>\u003Cp>Approximate version format example: 15.1.2375\u003C\u002Fp>\u003Cp>Approximate version filtering method:\u003C\u002Fp>\u003Cp>Truncate the Build number string by removing the data after the last character \".\", then compare it with the approximate version and output all results.\u003C\u002Fp>\u003Cp>Code example:\u003C\u002Fp>\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd>\u003Cp>versionarray = [\u003Cbr>[\"Exchange Server 2019 CU11 Mar22SU\", \"March 8, 2022\", \"15.2.986.22\"],\u003Cbr>[\"Exchange Server 2019 CU11 Jan22SU\", \"January 11, 2022\", \"15.2.986.15\"],\u003Cbr>[\"Exchange Server 2019 CU11 Nov21SU\", \"November 9, 2021\", \"15.2.986.14\"],\u003Cbr>[\"Exchange Server 2019 CU11 Oct21SU\", \"October 12, 2021\", \"15.2.986.9\"],\u003Cbr>[\"Exchange Server 2019 CU11\", \"September 28, 2021\", \"15.2.986.5\"],\u003Cbr>[\"Exchange Server 2019 CU10 Mar22SU\", \"March 8, 2022\", \"15.2.922.27\"]\u003Cbr>]\u003Cbr>version=\"15.2.986\"\u003Cbr>for value in versionarray:\u003Cbr>    if version in value[2][:value[2].rfind(\".\")]:\u003Cbr>        print(\"[+] Version: \" + value[2])\u003Cbr>        print(\"    Product: \" + value[0])\u003Cbr>        print(\"    Date: \" + value[1])\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch3>2. Vulnerability Detection\u003C\u002Fh3>\u003Cp>Using patch time as the basis for judgment, and similarly to improve efficiency, storing known vulnerability information in a list, with elements including release date and vulnerability number\u003C\u002Fp>\u003Cp>To facilitate time comparison, it is necessary to change the time format, for example, modifying September 28, 2021 to 09\u002F28\u002F2021\u003C\u002Fp>\u003Cp>Code example:\u003C\u002Fp>\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd>\u003Cp>vularray = [\u003Cbr>[\"CVE-2020-0688\", \"02\u002F11\u002F2020\"],\u003Cbr>[\"CVE-2021-26855+CVE-2021-27065\", \"03\u002F02\u002F2021\"],\u003Cbr>[\"CVE-2021-28482\", \"04\u002F13\u002F2021\"]\u003Cbr>]\u003Cbr>date=\"03\u002F01\u002F2021\"\u003Cbr>for value in vularray:\u003Cbr>    if (date.split('\u002F')[2] < value[1].split('\u002F')[2]):\u003Cbr>        print(\"[+] \" + value[0] + \", \" + value[1])\u003Cbr>    else:\u003Cbr>        if (date.split('\u002F')[2] == value[1].split('\u002F')[2]) & (date.split('\u002F')[0] < value[1].split('\u002F')[0]):\u003Cbr>            print(\"[+] \" + value[0] + \", \" + value[1])\u003Cbr>        else:\u003Cbr>            if (date.split('\u002F')[2] == value[1].split('\u002F')[2]) & (date.split('\u002F')[0] == value[1].split('\u002F')[0]) & (date.split('\u002F')[1] < value[1].split('\u002F')[1]):\u003Cbr>                print(\"[+] \" + value[0] + \", \" + value[1])\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch2>0x04 Open Source Code\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Cp>Due to the length of the code content, the complete implementation code has been uploaded to GitHub at the following address:\u003C\u002Fp>\u003Cp>An open-source project\u003C\u002Fp>\u003Cp>The version database date is 03\u002F21\u002F2022\u003C\u002Fp>\u003Cp>Vulnerability information includes the following identifiers:\u003C\u002Fp>\u003Cul>\u003Cli>CVE-2020-0688\u003C\u002Fli>\u003Cli>CVE-2021-26855+CVE-2021-27065\u003C\u002Fli>\u003Cli>CVE-2021-28482\u003C\u002Fli>\u003Cli>CVE-2021-34473+CVE-2021-34523+CVE-2021-31207\u003C\u002Fli>\u003Cli>CVE-2021-31195+CVE-2021-31196\u003C\u002Fli>\u003Cli>CVE-2021-31206\u003C\u002Fli>\u003Cli>CVE-2021-42321\u003C\u002Fli>\u003C\u002Ful>\u003Cp>The code can automatically identify the exact version; if identification fails, it switches to identifying the approximate version and marks all matching vulnerabilities.\u003C\u002Fp>\u003Ch2>0x05 Summary\u003C\u002Fh2>\u003Cp>---\u003C\u002Fp>\u003Cp>This article introduces two methods for Exchange version detection using Python, detailing their implementation, providing open-source code, and serving as an excellent learning example.\u003C\u002Fp>\u003C\u002Fbody>\u003C\u002Fhtml>",4,"Onedaysec","published","2026-02-02T07:25:19.683Z",{"title":36,"description":14,"keywords":37,"ogImage":38,"canonicalUrl":38,"noIndex":39},"Exchange Version Detection & Vulnerability Scanning with Python","Exchange version detection, vulnerability scanning, Python, penetration testing, Exchange security, CVE-2020-0688, EWS interface, OWA interface, build number, patch date",null,false,[],{"docs":42,"hasNextPage":39},[43,44,45,4],1228,1227,1226,{"title":38,"description":38,"image":38},"2026-07-24T15:37:08.785Z","2026-07-23T16:02:41.836Z","draft","2026-07-23T16:17:30.722Z"]