Passbolt Api Retrieval of HTTP-only cookies
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-209.
Summary
Passbolt uses three cookies: a session cookie, a CSRF protection cookie and a cookie to keep track of the multiple-factor authentication process. Both the session cookie and the mfa cookie are properly set HTTP-only to prevent an attacker from retrieving the content of those cookies if they managed to exploit an XSS. The /auth/verify.json endpoint returns a JSON that, among other things, contains the cookies sent in the request. (similar to the TRACE HTTP method) An attacker who manages to leverage an XSS vulnerability could retrieve the session cookies of a legitimate user, effectively granting them the ability to retrieve information (such as encrypted password list or group list) without requiring user interaction. This vulnerability has a low impact, but no immediate risk due to it requiring the exploitation of an XSS vulnerability that has yet to be found.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | passbolt/passbolt_api (Packagist) | before 2.7.0 | 2.7.0 | Patch available | GHSA-f5pp-pmq8-gp46 |
- passbolt/passbolt_api (Packagist) Vendor— Affected before 2.7.0 Fixed in 2.7.0 Patch available GHSA-f5pp-pmq8-gp46
Remediation
- Fix · GHSA-f5pp-pmq8-gp46 passbolt/passbolt_api (Packagist) Fixed in 2.7.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-f5pp-pmq8-gp46
References
Other 4
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences