nodejs / nodejs/undici

Please review proposed OSS-Fuzz integration

Open
#5,154 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
7.7k
Forks
879
Avg merge
2d 16h
Merged PRs (30d)
68

Description

Hi Undici maintainers,

I opened an OSS-Fuzz PR to add an initial fuzzing integration for Undici:

https://github.com/google/oss-fuzz/pull/15453

The integration currently adds Jazzer.js fuzz targets for:

  • Headers, Request, and Response construction/header handling
  • undici.request using MockAgent, with network access disabled
  • fetch with FormData using a mocked response

Could someone from the Undici/Node.js maintainer side please take a look at the OSS-Fuzz PR and confirm two things?

  1. Whether security@nodejs.org is the right primary_contact for this OSS-Fuzz project, or whether another Google-account-backed maintainer/project email should be used.
  2. If the integration looks okay from the project side, could you please leave an LGTM/comment on the OSS-Fuzz PR? OSS-Fuzz usually wants maintainer approval before accepting a new project integration.

One implementation note: the PR is pinned to the v6.x branch for now because current Undici releases require a newer Node.js runtime than the OSS-Fuzz JavaScript base image currently provides.

Thanks!

Contributor guide

Open the contributing guide

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.

Research direction

Start with the linked OSS-Fuzz PR and review its Jazzer.js targets for Headers, Request, Response, undici.request, and fetch with FormData, including the v6.x runtime constraint. Done means confirming the appropriate primary_contact and, if the integration is acceptable, leaving the requested maintainer LGTM or comment on the OSS-Fuzz PR.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.