CyberRota Analysis
AI-GeneratedForgejo versions 13.0.0 through 16.0.4 are vulnerable when federation is enabled, allowing remote attackers to spoof identities by submitting valid ActivityPub activities attributed to any actor they specify. This vulnerability impacts identity integrity but does not permit account takeover or content modification. Organizations using affected Forgejo versions with federation enabled should prioritize addressing this issue to mitigate the risk of identity spoofing in their systems.
Original NVD Description
Forgejo 13.0.0 through 16.0.4, when "[federation] ENABLED = true" is set, has a spoofing issue that affects identity integrity but does not allow account takeover or content modification. It does not verify that the HTTP Signature on an incoming ActivityPub activity was produced by the key belonging to the actor named in the activity body. The signature verification in routers/api/v1/activitypub/reqsignature.go validates the request signature, but the inbox activity handlers subsequently read the acting identity from the attacker-controlled JSON body without binding it to the verified signing key. Additionally, the signed Digest header is not recomputed against the received request body. A remote attacker who hosts a single valid ActivityPub actor and keypair can therefore submit signature-valid activities attributed to any actor identity they name.