Only the latest release on the JetBrains Marketplace gets security fixes. Update the plugin (Settings › Plugins › Installed › Comark › Update) before you report a problem.
Don't open a public issue for a security problem. Report it privately through GitHub:
- Open the repository's Security tab.
- Choose Report a vulnerability and fill in the form.
Include what you can of:
- the plugin version and the IDE (name, version, operating system);
- what an attacker can do, and under which conditions (for example: opening a crafted Markdown file, a malicious
content.config.tsorpackage.jsonin a cloned project, rendering a document in the preview); - steps or a minimal file that reproduce it.
You can expect an acknowledgement within a week. Once the problem is confirmed, a fix is released as soon as possible and the advisory is published with the release. You are credited in the advisory unless you prefer not to be.
The plugin reads files of the open project (Markdown, Vue components, package.json, lockfiles, content.config.ts,
nuxt.config.ts), renders Markdown in the IDE's preview, and can fetch component metadata from a URL you configure. Problems
in these areas are in scope, for example:
- code or script execution, or network access, triggered by opening or previewing a file;
- reading files outside the project, or leaking their content;
- the IDE hanging or running out of memory on a small crafted file (report these as security problems only when one file is enough to make the IDE unusable; slow formatting of a huge file is a normal bug).
Vulnerabilities in the IntelliJ Platform, the bundled Markdown plugin or JCEF belong to JetBrains instead.