Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

GHSA-f36p-42jv-8rh2 lithium

HIGHFix: wireapp/lithium@8b9b406

GHSA-f36p-42jv-8rh2 is a high-severity (CVSS 8.1) remote code execution vulnerability in com.wire:lithium. A fix is available for com.wire:lithium — see the affected versions and patch details below.

Lithium vulnerable to Cross Site Scripting in provided Swagger-UI

Published
Sep 30, 2022
Updated
Nov 28, 2024
Affected
2 pkgs
Patched
1 / 2
Exploits
None indexed
Exploitation data as of Nov 28, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
com.wire:lithiumcom.wire.bots:lithium

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A XSS vulnerability in the provided (outdated) Swagger-UI is exploitable in applications using lithium with Swagger-UI enabled. This allows an attacker gain Remote Code Execution (RCE) and potentially exfiltrate secrets in the context of this swagger session.

Patches

The used swagger-ui was updated by switching to the latest version of dropwizard-swagger in 8b9b406d608fe482ec0e7adf8705834bca92d7df

Workarounds

The risk of injected external content can be reduced by setting up a Content-Security-Policy.

References

Credits

We thank Mohit Kumar for reporting this vulnerability!

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.wire:lithiumall versions3.4.2com.wire:lithium:3.4.2
Mavencom.wire.bots:lithiumall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.wire:lithium, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.wire:lithium to 3.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f36p-42jv-8rh2 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f36p-42jv-8rh2 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f36p-42jv-8rh2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A XSS vulnerability in the provided (outdated) Swagger-UI is exploitable in applications using lithium with Swagger-UI enabled. This allows an attacker gain Remote Code Execution (RCE) and potentially exfiltrate secrets in the context of this swagger session. ### Patches The used swagger-ui was updated by switching to the latest version of dropwizard-swagger in 8b9b406d608fe482ec0e7adf8705834bca92d7df ### Workarounds The risk of injected external content can be reduced by setting up a [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Se
O3 Security · Impact-Aware SCA

Is GHSA-f36p-42jv-8rh2 in your dependencies?

O3 Security finds GHSA-f36p-42jv-8rh2 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-f36p-42jv-8rh2: lithium RCE (High 8.1) | O3 Security