Skip to content

Security: HeftyB/mdtools

Security

SECURITY.md

Security Policy

Supported versions

mdtools is pre-1.0; security fixes are applied to the latest released minor version and main. Older pre-1.0 versions are not maintained.

Version Supported
main / latest release ✅
older pre-1.0 tags ❌

Reporting a vulnerability

Please do not open a public issue for security vulnerabilities.

Report privately to andrew@duvalanalytics.com with:

  • a description of the issue and its impact,
  • steps to reproduce (a minimal Markdown input, command line, and platform),
  • any suggested remediation if you have one.

If your Gitea instance has private vulnerability reporting enabled, you may use that channel instead.

What to expect

  • Acknowledgement within 5 business days.
  • An assessment and, for confirmed issues, a remediation plan with a target timeline shared with you.
  • Coordinated disclosure: we will agree on a disclosure date with you and credit you in the release notes unless you prefer to remain anonymous.

Scope and threat model

mdtools parses and renders untrusted Markdown files. The most sensitive area is the parser (core/), which processes arbitrary input in C. Memory-safety issues (buffer overreads/overflows, use-after-free), crashes/denial-of-service on malformed input, and any path that could execute or leak beyond rendering are in scope.

The parser is built and tested under AddressSanitizer and UndefinedBehavior Sanitizer in CI (see docs/ROADMAP.md); reproducers that trip a sanitizer are especially welcome.

There aren't any published security advisories