Skip to content

Lithium vulnerable to Cross Site Scripting in provided Swagger-UI

High severity GitHub Reviewed Published Sep 27, 2022 in wireapp/lithium • Updated Jan 12, 2023

Package

maven com.wire.bots:lithium (Maven)

Affected versions

< 3.4.2

Patched versions

None
maven com.wire:lithium (Maven)
< 3.4.2
3.4.2

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!

References

@comawill comawill published to wireapp/lithium Sep 27, 2022
Published to the GitHub Advisory Database Sep 30, 2022
Reviewed Sep 30, 2022
Last updated Jan 12, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-f36p-42jv-8rh2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.