dbcve.org
Skype ExtensionPlugin / extension · Microsoft

CVE-2022-24522

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-09
Fix available
A fix is available. Upgrade to 10.2.0.9951 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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
Skype Extension for Chrome Information Disclosure Vulnerability

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

This is an information disclosure vulnerability in the Skype Extension for Chrome. The vulnerability allows unintended access to sensitive information through the extension, likely due to improper access controls or cross-origin data handling within the browser extension context.

MitigationUsers should update the Skype Extension for Chrome to the latest patched version, or remove the extension if an update is not available. Organizations may also consider disabling the extension until a patch is applied.

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
Skype ExtensionPlugin / extension
Affected:< 10.2.0.9951

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Skype Extension for Chrome is installed
    Open Chrome and navigate to chrome://extensions. Look for the 'Skype' extension in the list of installed extensions. Alternatively, click the puzzle piece icon in Chrome's toolbar to view installed extensions.
    Affected if The Skype Extension appears in the list of installed Chrome extensions
  2. Determine the installed version number
    In chrome://extensions, enable 'Developer mode' (toggle in top right). Locate the Skype Extension and read the version number displayed in its card. Note the full version string (e.g., 10.2.0.9951).
    Affected if A version number is displayed for the Skype Extension
  3. Compare version against vulnerable range
    Take the installed version number and compare it numerically to 10.2.0.9951. Any version lower than 10.2.0.9951 (e.g., 10.1.0.1234, 9.5.0.0) is within the vulnerable range.
    Affected if Installed version is less than 10.2.0.9951 (e.g., 10.1.x.x, 9.x.x.x, etc.)
  4. Confirm the extension is enabled
    In chrome://extensions, verify the toggle next to the Skype Extension is in the 'on' position. An enabled extension runs in the browser context and could expose the vulnerability.
    Affected if The Skype Extension toggle is enabled (turned on)

You are affected if the Skype Extension for Chrome is installed, enabled, and running a version lower than 10.2.0.9951.

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.

dbcve · scoped
Upgrade available Upgrade to 10.2.0.9951 or later
Fixed in 10.2.0.9951
Interim mitigation

Users should update the Skype Extension for Chrome to the latest patched version, or remove the extension if an update is not available. Organizations may also consider disabling the extension until a patch is applied.

Recommended fix High confidence

10.2.0.9951

  1. Open the Google Chrome browser
  2. Navigate to the Chrome Web Store page for the Skype extension (search for 'Skype' in the Chrome Web Store)
  3. Check the current installed version by navigating to chrome://extensions and enabling Developer mode
  4. Locate the Skype Extension and verify the version number
  5. If the installed version is below 10.2.0.9951, click 'Update' on the extension card, or reinstall the extension from the Chrome Web Store to get the latest version
  6. Restart Chrome and verify the updated version number in chrome://extensions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Skype Extension Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24522 — 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-2022-24522 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