dbcve.org
Webex TeamsApplication · Cisco

CVE-2024-20395

HIGH · 7.3 CVSS v3.1 Published 2024-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
No privileges

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 in the media retrieval functionality of Cisco Webex App could allow an unauthenticated, adjacent attacker to gain access to sensitive session information. This vulnerability is due to insecure transmission of requests to backend services when the app accesses embedded media, such as images. An attacker could exploit this vulnerability by sending a message with embedded media that is stored on a messaging server to a targeted user. If the attacker can observe transmitted traffic in a privileged network position, a successful exploit could allow the attacker to capture session token information from insecurely transmitted requests and possibly reuse the captured session information to take further actions as the targeted user.

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 · high confidence

The Cisco Webex App media retrieval functionality transmits requests for embedded media (images) to backend services over insecure channels. An adjacent attacker with visibility into network traffic can capture session tokens from these unencrypted requests and potentially reuse them to impersonate the targeted user.

MitigationApply vendor-provided patches when available. In the interim, enforce network-level protections such as VPN usage, network segmentation, and TLS inspection to limit adjacent attack surface.

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
Webex TeamsApplication
Affected:= 3.0.13464.0= 3.0.13538.0= 3.0.13588.0= 3.0.14154.0= 3.0.14234.0= 3.0.14375.0= 3.0.14741.0= 3.0.14866.0= 3.0.15015.0= 3.0.15036.0= 3.0.15092.0= 3.0.15131.0

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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Verify Cisco Webex Teams is installed
    Check for the application in standard installation directories or use system package management tools (e.g., Windows: check Program Files for 'Webex Teams' folder, macOS: check /Applications for Webex Teams.app, Linux: check dpkg or rpm packages)
    Affected if The application is present on the system
  2. Determine installed version number
    Open Cisco Webex Teams, navigate to Help > About, or check the application's properties/metadata file for the exact version string
    Affected if Unable to retrieve version information but application is installed
  3. Compare version against affected list
    Match the installed version against: 3.0.13464.0, 3.0.13538.0, 3.0.13588.0, 3.0.14154.0, 3.0.14234.0, 3.0.14375.0, 3.0.14741.0, 3.0.14866.0, 3.0.15015.0, 3.0.15036.0, 3.0.15092.0, 3.0.15131.0
    Affected if Installed version exactly matches any version in the affected list
  4. Verify media retrieval uses insecure channels (optional investigation)
    Use a network capture tool (e.g., Wireshark) while the application retrieves embedded media; inspect if HTTP (port 80)而非HTTPS (port 443) is used for image requests
    Affected if HTTP requests containing session tokens are observed in network traffic for media retrieval

User is affected if Cisco Webex Teams is installed and the installed version exactly matches any of the listed affected versions (3.0.13464.0 through 3.0.15131.0).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches when available. In the interim, enforce network-level protections such as VPN usage, network segmentation, and TLS inspection to limit adjacent attack surface.

Fix this in Webex Teams Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2024-20395 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