envoyproxy / envoyproxy/envoy

Audit YAML parsing code path

Open
#9,039 1 comment 0 reactions 0 assignees View on GitHub
area/security help wanted tech debt
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
428

Description

The YAML parser we're using are not robust to untrust input, it should only be used to parse local file. We should add some basic limitation in the code base to prevent it happening.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the YAML parser code path and identifying where input enters the parser. Review how local files and potentially untrusted input are distinguished; done means basic limitations prevent unsafe use with untrusted input while preserving the intended local-file behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, yaml
Domain
backend, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.