Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unverified sandbox items from the Oct 11 audit: proxy checks only the TLS name, and stacked drive-letter definitions

Open
#293 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
desktop, security

Research direction

Read src/main/tools/net_proxy.ts:222-230 and native/sandbox-helper/src/win.rs, then verify both reported behaviors: the proxy's handling of CONNECT and TLS ClientHello extensions, and how QueryDosDeviceW definitions are checked. The issue proposes documenting the proxy limit or refusing ECH, and comparing only the first drive mapping entry; completion means both findings are verified and the chosen fixes prevent the described behavior.

Written by the indexing model from the issue text.

Description

priority: low security severity: low

Found in the Oct 11 audit (at c5f5641). Both need verification.

  1. The allow-list proxy checks only the TLS server name (src/main/tools/net_proxy.ts:222-230). A CONNECT to an allowed host on a shared CDN can send Host: other-site inside TLS (domain fronting), and Encrypted Client Hello hides the real name behind the CDN's public name. Fix: document the limit, or refuse a ClientHello that carries an ECH extension (0xfe0d).
  2. DriveMapping::is_live accepts any entry of a drive letter's definition stack (native/sandbox-helper/src/win.rs, added in 68dd655). QueryDosDeviceW returns every stacked definition, and .any(...) accepts the expected target even when another definition sits on top, so ProjectDrive::define skips DefineDosDeviceW and the run starts in the wrong folder. Correctness only: access is still governed by ACLs. Fix: compare only the first entry.
Dominant language
TypeScript
Stars
2
Forks
2
Avg merge
5h 28m
Merged PRs (30d)
24

Getting set up

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 PierrunoYT/patch

All issues in PierrunoYT/patch

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.