Is CVE-2023-23635 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2023-23635 being exploited in the wild.

How severe is CVE-2023-23635?

Low severity, with a CVSS score of 3.1, published 3 February 2023.

Which products and versions are affected?

jellyfin-web (npm) SEMVER:introduced=10.8.0,fixed=10.8.4.

Is there a fix for CVE-2023-23635?

Yes. jellyfin-web (npm): upgrade to 10.8.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2023-23635 attacked?

It is attacked over the network.

Am I affected by CVE-2023-23635?

Check whether you run jellyfin-web (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2023-23635: Jellyfin Web stored cross-site scripting in collection name

CVE-2023-23635 · Severity: low · CVSS 3.1 · Published 2023-02-03

Jellyfin Web is a browser-based interface for managing and viewing media content in a Jellyfin media server. A stored XSS vulnerability in collection names allows attackers to inject malicious scripts that execute when other users view collections, potentially stealing authentication tokens and compromising user accounts.

Vendors: npm.

Quick answers

Is CVE-2023-23635 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2023-23635 being exploited in the wild.
How severe is CVE-2023-23635?: Low severity, with a CVSS score of 3.1, published 3 February 2023.
Which products and versions are affected?: jellyfin-web (npm) SEMVER:introduced=10.8.0,fixed=10.8.4.
Is there a fix for CVE-2023-23635?: Yes. jellyfin-web (npm): upgrade to 10.8.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2023-23635 attacked?: It is attacked over the network.
Am I affected by CVE-2023-23635?: Check whether you run jellyfin-web (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

jellyfin-web (npm): upgrade to 10.8.4 or later
```
npm install jellyfin-web@10.8.4
```

Technical details

The vulnerability is a stored cross-site scripting (XSS) flaw in Jellyfin Web versions 10.8.0 through 10.8.3, classified as CWE-79. The root cause is improper HTML escaping of item/collection names when rendering aria-labels in item card components. An attacker with the ability to edit item/collection names can inject malicious JavaScript payloads (e.g., <img src=/X onerror=alert("xss")>) that execute in the browser context of any user viewing the affected collection. The attack requires authenticated access to create or modify collections, and user interaction (viewing the affected content), but can result in theft of localStorage-stored access tokens. The vulnerability was fixed in version 10.8.4.

Affected products

Jellyfin Jellyfin Web 10.8.0 through 10.8.3

Identifiers

CVE-2023-23635
GHSA-749c-pc87-4qcw

Timeline

2023-02-03: disclosed: GHSA advisory published
2023-02-03: patched: Fixed in Jellyfin 10.8.4

References

https://github.com/jellyfin/jellyfin-web/issues/3788

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.