prometheus/prometheus

Fuzz test Prometheus APIs

Open

#667 opened on May 2, 2015

View on GitHub
 (13 comments) (0 reactions) (0 assignees)Go (64,042 stars) (10,408 forks)batch import
help wantedkind/enhancementpriority/P3

Description

Just found this new tool for Go: https://github.com/dvyukov/go-fuzz

Given that it found quite a few bugs in the standard library, we will certainly find some stuff in Prometheus. Especially as we are now using two text/template style parsers ourselves that might suffer from very similar bugs as the ones found in the stdlib.

Contributor guide

Tech stack
go
Domain
testingbackendobservability
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingbasic fuzzing conceptsPrometheus API knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate using go fuzz (https://github.com/dvyukov/go fuzz) to create fuzz tests for Prometheus APIs, particularly focusing on the text/template parsers mentioned in the issue. Review existing test files in the repository for patterns. Engage with maintainers via issue #667 comments for clarification on which specific APIs or parsers to target and any existing fuzzing efforts. The goal is to write fuzz functions that can uncover bugs similar to those found in the standard library.