GHSA-2f46-4xjm-73x5 Passbolt API Stored XSS on first/last name during setup
A malicious administrator can inject scripts into user setup pages via stored XSS in name fields, potentially tricking users into installing extensions.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is GHSA-2f46-4xjm-73x5?
GHSA-2f46-4xjm-73x5 is a cross-site scripting vulnerability in passbolt/passbolt_api, published on 20 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official description
Description
An administrator can craft a user with a malicious first name and last name, using a payload such as
<svg onload="confirm(document.domain)">'); ?></svg>
The user will then receive the invitation email and click on the setup link. The setup start page served by the server will fire the XSS.
Impact of issue
An administrator could use this exploit to edit the setup start page for a given user, for example, trick the user into installing another extension. Even though the severity of this issue in itself is high, the likelihood is low because the exploit will be visible in clear by the user in the email notification, and also requires an action from a malicious administrator.
Fix
Sanitize the firstname and lastname in the page that is used to trigger the extension setup process.
Additionally since v2.11 some default CSP are inserted in the server response headers to prevent inline-scripts or 3rd party domain scripts on pages served by the passbolt API. This is to cater for the case where the administrator has not set them up as part of the web server configuration.
Which versions are affected by GHSA-2f46-4xjm-73x5?
2 open source packages ship an affected version, including passbolt/passbolt_api.
| Package | Affected | Fixed in |
|---|---|---|
passbolt/passbolt_api Packagist | All versions | 2.11.0 |
passbolt/passbolt_api Packagist | All versions | 2.11.0 |
How do I fix GHSA-2f46-4xjm-73x5?
Upgrade passbolt/passbolt_api to 2.11.0 or later.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is GHSA-2f46-4xjm-73x5 being exploited?
There is no known exploitation of GHSA-2f46-4xjm-73x5 in the wild and no public exploit code.