Skip to content

Scanning Engine v2 - Module - Exchange OWA

Overview

Targeting

Schemas

The schema for the body object of all results generated with .task.module_name equal to exchange-owa can be found here. The schema for results is available both in standalone and bundled form.

Examples

These are examples of the .body object for results with .task.module_name equal to exchange-owa.

Microsoft Exchange 2016

This example was generated with a live host on the internet.

{
  "disposition": "on-premise",
  "version": {
    "build_version": "15.1.2507.39",
    "build_name": "Exchange Server 2016 CU23 Apr24HU",
    "release_date": "2024-04-23",
    "release_days": 140
  },
  "server_names": [
    "[REDACTED]"
  ],
  "ecp_enabled": true,
  "ews_enabled": true,
  "rpc_enabled": true
}

Microsoft Exchange 2019

This example was generated with a live host on the internet.

{
  "disposition": "on-premise",
  "version": {
    "build_version": "15.2.1544.9",
    "build_name": "Exchange Server 2019 CU14 Mar24SU",
    "release_date": "2024-03-12",
    "release_days": 182
  },
  "server_names": [
    "[REDACTED]"
  ],
  "ecp_enabled": true,
  "ews_enabled": true,
  "rpc_enabled": true
}

Changelog

v1.1.0 (2026-10-09)

  • Add the October 2, 2026 security update builds to the known Exchange version database: Exchange Server SE RTM Sep26SUv2 (15.2.2562.53), Exchange Server 2019 CU15 Sep26SUv2 (15.2.1748.53), Exchange Server 2019 CU14 Sep26SUv2 (15.2.1544.48), and Exchange Server 2016 CU23 Sep26SUv2 (15.1.2507.75).
  • The shared HTTP client in pkg/scanner now closes response bodies without reading them to EOF. Keep-alives are already disabled, so draining unread bytes could block the worker until the shard was killed when a target streamed or trickled a response.

v1.0.0 (2025-05-05)

  • Initial release of versioning for each module. All modules are being tagged with version number 1.0.0. Going forward:
  • Major version should be changed when there are changes that impact consumers or clients of the modules.
  • Minor version should be changed when there are additions which enrich or enhance the module but shouldn't affect consumers or clients.
  • Patch version should be changed when there are bugfixes.