Equinox ConferencingApplication · Avaya

CVE-2020-7038

HIGH · 7.5 CVSS v3.1 Published 2021-04-28
Fix available
A fix is available. Upgrade to 9.1.11 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was discovered in Management component of Avaya Equinox Conferencing that could potentially allow an unauthenticated, remote attacker to gain access to screen sharing and whiteboard sessions. The affected versions of Management component of Avaya Equinox Conferencing include all 3.x versions before 3.17. Avaya Equinox Conferencing is now offered as Avaya Meetings Server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An unauthenticated remote attacker can gain access to screen sharing and whiteboard sessions through the Management component of Avaya Equinox Conferencing versions before 3.17. The exact vulnerability type (e.g., IDOR, broken access control) is not specified in available documentation.

MitigationUpgrade Avaya Equinox Conferencing Management component to version 3.17 or later, or migrate to Avaya Meetings Server.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Equinox ConferencingApplication
Affected:>= 9.0.0, < 9.1.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Avaya Equinox Conferencing version
    Locate the installed Avaya Equinox Conferencing Management component and check its version number. This is typically found in the application's about page, installation directory, or system information panel.
    Affected if The installed version is 9.0.0 or higher but lower than 9.1.11
  2. Verify Management component is exposed
    Determine if the Avaya Equinox Conferencing Management web interface is accessible from the network. Check the listening services on the server and review firewall rules or network access controls.
    Affected if The Management component web interface is reachable from an untrusted network without proper network segmentation
  3. Confirm screen sharing and whiteboard are enabled
    Log into the Management interface and navigate to the session or collaboration settings. Check whether screen sharing and whiteboard features are enabled for users.
    Affected if Screen sharing or whiteboard features are enabled in the conferencing configuration
  4. Test unauthenticated access to sessions
    From an untrusted network perspective, attempt to access screen sharing or whiteboard session URLs without providing credentials. Observe whether the server permits access to active sessions without authentication.
    Affected if Unauthenticated access to screen sharing or whiteboard sessions is permitted without login

The environment is affected if Avaya Equinox Conferencing Management version is 9.0.0 through 9.1.10 and the Management interface with screen sharing/whiteboard features is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 9.1.11 or later
Fixed in 9.1.11
Interim mitigation

Upgrade Avaya Equinox Conferencing Management component to version 3.17 or later, or migrate to Avaya Meetings Server.

Fix this in Equinox Conferencing Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7038 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-7038 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data