Skip to content

Security: demaconsulting/DoxygenTool

SECURITY.md

Security Policy

Supported Versions

We release patches for security vulnerabilities for the following versions:

Version Supported
Latest
< Latest

Reporting a Vulnerability

If you discover a security vulnerability within DoxygenTool, please send an email to the maintainers. All security vulnerabilities will be promptly addressed.

Please do not report security vulnerabilities through public GitHub issues.

What to Include

When reporting a vulnerability, please include:

  • Type of vulnerability
  • Full paths of source file(s) related to the vulnerability
  • Location of the affected source code (tag/branch/commit or direct URL)
  • Any special configuration required to reproduce the issue
  • Step-by-step instructions to reproduce the issue
  • Proof-of-concept or exploit code (if possible)
  • Impact of the issue, including how an attacker might exploit it

Response Timeline

  • We will acknowledge your email within 48 hours
  • We will provide a detailed response within 7 days
  • We will work on a fix and keep you updated on progress
  • We will notify you when the vulnerability is fixed

Security Update Process

  1. The vulnerability is received and assigned to a primary handler
  2. The problem is confirmed and affected versions are determined
  3. Code is audited to find similar problems
  4. Fixes are prepared for all supported versions
  5. New versions are released with security patches

Comments on This Policy

If you have suggestions on how this process could be improved, please submit a pull request or open an issue.

There aren’t any published security advisories