prometheus / prometheus/alertmanager

Add Alertmanager to the OSS-Fuzz project

Open
#4,912 0 comments 0 reactions 1 assignee View on GitHub

@SoloJacobs is already working on this.

Since Jan 25, 2026.

kind/enhancement
Dominant language
Go
Stars
8.6k
Forks
2.5k
Avg merge
2d 6h
Merged PRs (30d)
61

Description

Proposal

prometheus/prometheus is already part of OSS-Fuzz, see here. We would also benefit from fuzzing in some parts of Alertmanager. This is easy to appreciate if one adds a simple fuzzer, which tests the config.Load function, where a fuzzer can easily detect bugs. An example

global:
route:
receivers:
- name: "example"
  webhook_configs:
  -

Results in

./amtool check-config --output=json config/testdata/conf.crash.yaml
Checking 'config/testdata/conf.crash.yaml'panic: runtime error: invalid memory address or nil pointer dereference [recovered, repanicked]
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0xae3398]

goroutine 1 [running]:
gopkg.in/yaml%2ev2.handleErr(0xc000311a28)

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.