Security readout for executives and security teams
Plain-English summary
This is a high-impact Microsoft Exchange Server remote code execution vulnerability. In business terms, a vulnerable legacy Exchange server could let an attacker run code after meeting the required access and interaction conditions. CISA lists it in KEV, so known exploitation is documented and legacy Exchange exposure should be treated as urgent.
Executive priority
Treat this as an urgent legacy Exchange remediation item, not a theoretical issue. The affected product is old, impact is high, and KEV confirms known exploitation. If the product is present, patch or remove it quickly and verify exposure reduction.
Technical view
CVE-2020-17144 affects Microsoft Exchange Server 2010 Service Pack 3 Update Rollup 31 in the supplied data. It is associated with CWE-502 and CVSS 3.1 score 8.4. The vector indicates network attack, low complexity, high privileges, required user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Organizations operating Microsoft Exchange Server 2010 SP3 Update Rollup 31 are the only affected product identified in the supplied data. Exposure is higher where legacy Exchange remains reachable by users or administrators. The bundle does not identify other Exchange versions or cloud services as affected.
Exploitation context
CISA KEV listing means known exploitation is documented. The CVSS vector indicates exploitation requires high privileges and user interaction. The supplied sources do not provide exploit mechanics, campaign details, or indicators, so those should not be inferred.
Researcher notes
Evidence supports affected scope, CVSS characteristics, CWE-502, Microsoft patch availability, and KEV status. The bundle does not include exploit details, indicators, or broad affected-version claims. Avoid expanding impact beyond Exchange Server 2010 SP3 Update Rollup 31 unless vendor sources confirm it.
Mitigation direction
- Apply the Microsoft security update referenced in the Microsoft advisory.
- Inventory and retire unsupported or legacy Exchange 2010 systems where possible.
- Restrict administrative and user access to vulnerable Exchange services until remediated.
- Check Microsoft guidance for any current compensating controls or update prerequisites.
- Prioritize KEV remediation tracking until the affected server is patched or removed.
Validation and detection
- Confirm whether Exchange Server 2010 SP3 Update Rollup 31 exists in the environment.
- Verify installed Exchange build and patch level against Microsoft’s CVE guidance.
- Check whether vulnerable Exchange systems are internet-facing or broadly reachable internally.
- Review logs and EDR telemetry for suspicious Exchange process activity.
- Document remediation status for KEV compliance and executive risk tracking.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-17144 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.4 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C1.76microsoftVulnerability scoring details
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- ADP timelineCISA-ADP
CVE-2020-17144 added to CISA KEV
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2021-11-03T00:00:00.000Z: CVE-2020-17144 added to CISA KEV
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft Exchange Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-17144CVE reference, CVE · x_refsource_MISC, x_transferred
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-17144CVE reference, CISA-ADP · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.