Matrix Matrix-appservice-bridge 9.0.0 for Node.js

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:matrix:matrix-appservice-bridge:9.0.0:*:*:*:*:node.js:*:*

part: a version: 9.0.0 update: *

VendorMatrix (eeffbdfc-c7a5-5b43-a123-a772af0b6d34)
ProductMatrix Appservice Bridge (b4af5485-64b3-5214-96f2-3411715481f6)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/matrix-org/matrix-appservice-bridge purl2cpe 2026-06-01 10:13:24.259338
pkg:npm/matrix-appservice-bridge purl2cpe 2026-06-01 10:13:24.259339

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-38691 vulnerable 2026-06-03 14:52:31.817790 matrix-appservice-bridge doesn't verify the sub parameter of an openId token exhange, allowing unauthorized access to provisioning APIs
MEDIUM (5)
matrix-appservice-bridge provides an API for setting up bridges. Starting in version 4.0.0 and prior to versions 8.1.2 and 9.0.1, a malicious Matrix server can use a foreign user's MXID in an OpenID exchange, allowing a bad actor to impersonate users when using the provisioning API. The library does not check that the servername part of the `sub` parameter (containing the user's *claimed* MXID) is the the same as the servername we are talking to. A malicious actor could spin up a server on any given domain, respond with a `sub` parameter according to the user they want to act as and use the resulting token to perform provisioning requests. Versions 8.1.2 and 9.0.1 contain a patch. As a workaround, disable the provisioning API.
Published: 2023-08-04T16:34:54.312Z
Updated: 2024-10-07T13:01:29.642Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.