Security: DoS via crafted TTF file. Please share security contact

Open
  • Is something wrong?
#368 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
javascript, node.js
Domain
security

Research direction

Start with issue #368 and the reported crash when accessing a composite glyph's path in fontkit v2.0.4. No file, test, or entry point is identified; progress depends on receiving the PoC privately, establishing a security contact, and completing vulnerability triage.

Written by the indexing model from the issue text.

Description

I've found vulnerabilities in fontkit that allow a small crafted TrueType font to crash a Node.js process when accessing a composite glyph's path. Affects v2.0.4 (current npm release). Do you have a private channel: security email or GitHub Security Advisory to share details and PoC files?

Dominant language
JavaScript
Stars
1.7k
Forks
254
Avg merge
1d 13h
Merged PRs (30d)
22

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from foliojs/fontkit

All issues in foliojs/fontkit

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.