a second, distinct DoS in fontkit, separate from #368

Open
  • Is something wrong?
#382 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
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
javascript
Domain
security

Research direction

No source file, test, or entry point is identified. Start by reviewing issue #368 and the repository's current security-reporting setup, then establish a private contact for the reporter; the issue is ready for further work when the PoC and suggested fix can be received and triaged confidentially.

Written by the indexing model from the issue text.

Description

Hi, separately from the TTF composite-glyph issue in #368, I've found a second, distinct security issue.

There's no SECURITY.md or private vulnerability reporting enabled here, so I can't share specifics publicly. Could you point me to a security contact? I will be happy to send a minimal PoC and a suggested fix privately.

Thanks!

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.