Reflected XSS in fava application in beancount/fava
Jul 22nd 2022
The "query_string" parameter of fava application is vulnerable to reflected XSS for which a attacker can modify any information that the user is able to modify.
Proof of Concept
1.Open the url:
2.Now XSS will popup.
If an attacker can control a script that is executed in the victim's browser, then they can typically fully compromise that user. Amongst other things, the attacker can:
+Perform any action within the application that the user can perform.
+View any information that the user is able to view.
+Modify any information that the user is able to modify.
Initiate interactions with other application users, including malicious attacks, that will appear to originate from the initial victim user. There are various means by which an attacker might induce a victim user to make a request that they control, to deliver a reflected XSS attack. These include placing links on a website controlled by the attacker, or on another website that allows content to be generated, or by sending a link in an email, tweet or other message
Since Fava URLs are dependent on the name of the underlying Beancount journal and the base URLs, which should be private and require a previous attach to be determined by the attacker, I've marked the attack complexity as "high"
You are welcome :) @maintainer
@admin Can you please update the CVE description in nvd/mitre
We are currently waiting for MITRE to accept our contribution here. Once they do, the CVE will go live 👍