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.0 release
- This fix will also be back-ported to the
0.7.x branch, applied to the 0.7.2 release
Workarounds
There are no workarounds for this issue, users should upgrade to a patched version.
References
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:
saharshtapi Analyst
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:
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
0.8.0release0.7.xbranch, applied to the0.7.2releaseWorkarounds
There are no workarounds for this issue, users should upgrade to a patched version.
References
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: