Fedify has an LD-Signature Bypass via JSON-LD Named-Graph Restructuring
fedify-dev fedify
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @fedify/fedify npm |
|
|
fedify-dev fedify
| Product | Affected | Fixed in |
|---|---|---|
| @fedify/fedify npm |
|
|
1.10.101.9.11Fedify is a TypeScript library for building federated server apps powered by ActivityPub. Prior to versions 1.9.11, 1.10.10, 2.0.18, 2.1.14, and 2.2.3, an attacker can make use of JSON-LD features to restructure a JSON-LD document that would change how Fedify interprets it without changing its Linked Data Signature, allowing them to alter a third-party signed activity they have received. Versions 1.9.11, 1.10.10, 2.0.18, 2.1.14, and 2.2.3 fix the issue.
From the CVE record · GitHub_M
Fedify can interpret a JSON-LD document differently after it is restructured, even though its Linked Data Signature remains unchanged. An attacker who has received a third-party signed activity can use this behavior to alter that activity without changing its signature; the input does not specify authentication or user-interaction requirements.
Teams using npm @fedify/fedify should check versions >=2.2.0 <2.2.3, >=2.1.0 <2.1.14, >=2.0.0 <2.0.18, >=1.10.0 <1.10.10, or <1.9.11.