- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Impact
InvenTree uses [EasyMDE](https://github.com/Ionaru/easy-markdown-editor) for displaying markdown text in various places (e.g. for the various "notes" fields associated with various models).
By default, EasyMDE does not sanitize input data, and it is possible for malicious code to be injected into the markdown editor, and executed in the users browser.
*Note: This malicious data must be first uploaded to the database by an authorized user, so the risk here is limited to trusted users*
### Solution
The solution here is two-fold:
- Enable data sanitization for the EasyMDE renderer - [#3205](https://github.com/inventree/InvenTree/pull/3205) - Enforce cleaning of all data uploaded to the database via the API - [#3204](https://github.com/inventree/InvenTree/pull/3204) *(This will be ready for the 0.8.0 release)*
### Patches
- The issue is addressed in the 0.8.0 release - This fix was back-ported to the 0.7.x branch, applied to the 0.7.3 release
### Workarounds
There is no workaround for this issue without upgrading InvenTree to the specified version.
### References
- https://huntr.dev/bounties/ab296cf5-7a3e-4f49-8f63-5b35fc707f03/
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github](http://github.com/inventree/inventree) * Email us at [security@inventree.org](mailto:security@inventree.org)
Patch / fix
- pypi inventree 0.7.3
Is GHSA-85q9-7467-r53q in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | inventree | <0.7.3 |
0.7.3 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
Sources
- GitHub Advisory GHSA-85q9-7467-r53q
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.