Tree listing filters on the owner instead of the requester
User node tree access-control is filtered by the owner username not the requester username.
This allows for an unauthenticated party to get a users node tree. Requires that the owner username is listed in the access-control of a node to list related nodes.
Used correct variable, also adjusted variable names to make it more clear for future.
- affected versions:
>= 1.0.0, <= 1.0.2 - patched versions:
>=1.0.3 - cwe:
CWE-863 - cve: ``
- score:
3.1/10 - credit:
- @arpitjain099 (reporter)
- more info: https://github.com/enchant97/note-mark/security/advisories/GHSA-7g73-5rrw-446p
No audience check during RFC 8693 token exchange
During token-exchange the access-token is used without validating the audience or client-id.
If a third-party app is exploited that uses the same authentication provider it is possible to use the same token to authenticate with Note Mark.
Added checks on the ID Token and ensure returned subject is matches when using the Access Token.
- affected versions:
>= 1.0.0, <= 1.0.2 - patched versions:
>=1.0.3 - cwe:
CWE-287CWE-346 - cve:
7.4/10 - score:
High - credit:
- @alham-rizvi (reporter)
- more info: https://github.com/enchant97/note-mark/security/advisories/GHSA-3j7j-3hq5-h3rp