Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-rm89-9g65-4ffr
No affected components available
Impact
Affected versions can have malicious javascript code injected into the users browser by other authenticated users, as data fields retrieved from the database are not properly sanitized before displaying in various front-end views.
The problem here stems from multiple issues:
- Insufficient database sanitation on multiple fields allows injection of un-sanitized HTML
- Lack of HTML escaping when rendering data on the front end
The attack vector here is limited, as only authenticated users are able to write data to the database, for it to be subsequently rendered on the front-end. However, it is a vulnerability that the InvenTree development team takes seriously.
Solution
The proposed patch for this vulnerability is prevents injection of un-escaped fields into front-end UI elements.
A future patch will also address sanitization of database fields on the "back end", however this will require a much larger effort to refactor multiple database tables.
Patches
- The issue is addressed in the upcoming
0.8.0release - This fix will also be back-ported to the
0.7.xbranch, applied to the0.7.2release
Workarounds
There are no workarounds for this issue, users should upgrade to a patched version.
References
- https://huntr.dev/bounties/4cae8442-c042-43c2-ad89-6f666eaf3d57/
- https://huntr.dev/bounties/9d640ef2-c52c-4106-b043-f7497d577078/
- https://huntr.dev/bounties/b114e82f-6c02-485b-82ea-e242f89169c2/
- https://huntr.dev/bounties/22783cd3-1b2c-48fc-b31f-03b53c86da0b/
Thank you @saharshtapi for bringing this issue to our attention and giving pointers for fixing them.
For more information
If you have any questions or comments about this advisory:
- Open an issue in github
- Email us at security@inventree.org
Measures severity based on intrinsic characteristics of the vulnerability, independent of environment.
No exploitation activity has been observed at this time. Continue routine monitoring.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard