Gitify before 7.10.0 contains a login cross-site request forgery vulnerability that allows remote attackers to bind a victim's client to their account because performGitHubWebOAuth() omits OAuth state validation. Attackers can get a gitify://oauth?code= link with their own authorization code opened during a victim's pending login, causing Gitify to display attacker-controlled notifications as the victim's own.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
Present
Additional conditions required
Privileges Required
None
No privileges needed
User Interaction
Passive
Minimal interaction
Impact Assessment
Confidentiality
None
No data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 5
https://github.com/gitify-app/gitify/blob/v7.9.0/src/renderer/utils/forges/gith…
disclosure@vulncheck.com
https://github.com/gitify-app/gitify/commit/10235b243e167a7c76eafd6a3d0ebc8c575…
disclosure@vulncheck.com
https://github.com/gitify-app/gitify/issues/3425
disclosure@vulncheck.com
https://github.com/gitify-app/gitify/releases/tag/v7.10.0
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/gitify-before-7.10.0-login-csrf-via-missin…
disclosure@vulncheck.com