Report Vulnerability

I have a report vulnerability of MATE Enviroment. I have taken a CVEID from Mitre but I have not published it anywhere. Can I send you the report? Do you publish it? Do I get a bounty?

1 Like

Hi, @MarziehHashemi :slight_smile:

(Usual disclaimer: please note that I'm just another Forum user here. I'm NOT an Ubuntu Developer and/or Ubuntu MATE Developer and/or MATE Developer).

You've asked:

That's a good question :thinking: From some web searches that I've done, I've found the following related discussion in an Issue - - in the "mate-desktop" repository - - in GitHub:

Related to that discussion, I've found the following relevant section of the "Privately reporting a security vulnerability - GitHub Docs" web page - :


  • You can only report a vulnerability privately for repositories where private vulnerability reporting is enabled, and you don't have to follow the instructions in the file. This reporting process is fully private, and GitHub notifies the repository administrators directly about your submission.

Privately reporting a security vulnerability

If you do not have admin or security permissions for a public repository, you can still privately report a security vulnerability to repository maintainers. You can also evaluate the general security of a public repository and suggest a security policy. For more information, see "Evaluating the security settings of a repository.

1. On, navigate to the main page of the repository.

2. Under the repository name, click Security. If you cannot see the "Security" tab, select the dropdown menu, and then click Security.Screenshot of a repository header showing the tabs. The "Security" tab is highlighted by a dark orange outline.

3. Click Report a vulnerability to open the advisory form.

4. Fill in the advisory details form.

Tip: In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the GitHub Security Lab, which is available on the github/securitylab repository."

For more information about the fields available and guidance on filling in the form, see "Creating a repository security advisory" and "Best practices for writing repository security advisories."

5. At the bottom of the form, click Submit report. GitHub will display a message letting you know that maintainers have been notified and that you have a pending credit for this security advisory.

Tip: When the report is submitted, GitHub automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.

6. Optionally, click Start a temporary private fork if you want to start to fix the issue. Note that only the repository maintainer can merge changes from that private fork into the parent repository.Screenshot of the bottom of a security advisory. A button, labeled "Start a temporary fork" is outlined in dark orange.

The next steps depend on the action taken by the repository maintainer. For more information, see "Managing privately reported security vulnerabilities. "

After reading that article, I see that the "mate-desktop" Repository in GitHub at least does have a "Security" page - - with a "Report a vulnerability" (green) button. SCREENSHOT:

I hope this helps :slight_smile:


Welcome @MarziehHashemi to the community!

1 Like