LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7037: Avaya Equinox Conferencing XXE vulnerability

An XML External Entities (XXE) vulnerability in Media Server component of Avaya Equinox Conferencing could allow an authenticated, remote attacker to gain read access to information that is stored on an affected system or even potentially lead to a denial of service. The affected versions of Avaya Equinox Conferencing includes all 9.x versions before 9.1.11. Equinox Conferencing is now offered as Avaya Meetings Server.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Avaya conferencing servers running affected 9.x versions have an XML parsing flaw that can let a logged-in remote attacker read sensitive local information or disrupt service. The issue affects the Media Server component and is rated high because exploitation needs low complexity but does require authentication.

Executive priority

Treat this as a priority remediation for organizations using Avaya conferencing infrastructure. It is not confirmed as actively exploited in the provided sources, but the business impact includes sensitive information exposure and conferencing service disruption.

Technical view

CVE-2020-7037 is a CWE-611 XML External Entity vulnerability in Avaya Equinox Conferencing Media Server, now Avaya Meetings Server. Affected versions are all 9.x releases before 9.1.11. CVSS 3.1 is 8.1: network exploitable, low complexity, low privileges, no user interaction, with high confidentiality and availability impact.

Likely exposure

Exposure is most likely where Avaya Equinox Conferencing or Avaya Meetings Server 9.x before 9.1.11 is deployed and reachable by authenticated remote users. The provided sources do not identify affected hosted services, appliances beyond this product, or specific internet exposure patterns.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires authenticated remote access. Confirmed potential outcomes are information disclosure from the affected system and possible denial of service.

Researcher notes

The evidence identifies product, affected version range, weakness class, CVSS vector, and vendor reference. It does not provide technical internals, indicators of compromise, proof-of-concept status, or detailed mitigation beyond moving off affected versions and following Avaya guidance.

Mitigation direction

  • Inventory Avaya Equinox Conferencing and Avaya Meetings Server deployments.
  • Upgrade affected 9.x versions before 9.1.11 to a non-affected vendor-supported release.
  • Review the Avaya advisory for supported fixes and operational constraints.
  • If upgrade is delayed, request Avaya-supported compensating controls.

Validation and detection

  • Check product and Media Server component versions against the 9.x before 9.1.11 affected range.
  • Confirm whether authenticated remote users can reach the affected conferencing service.
  • After remediation, verify the system no longer reports an affected version.
  • Review logs for unusual authenticated access or service disruption around XML-processing paths.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-611: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2020-7037 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2020-7037Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AvayaAvaya Meetings Server9.xListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-611 · source CWE mapping

Improper Restriction of XML External Entity Reference

Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.