Skip to content

fuzz: fixes oss-fuzz: 9599, 9600#3979

Merged
mattklein123 merged 2 commits intoenvoyproxy:masterfrom
anirudhmurali:master
Jul 31, 2018
Merged

fuzz: fixes oss-fuzz: 9599, 9600#3979
mattklein123 merged 2 commits intoenvoyproxy:masterfrom
anirudhmurali:master

Conversation

@anirudhmurali
Copy link
Copy Markdown
Member

@anirudhmurali anirudhmurali commented Jul 28, 2018

Title: Fixes oss-fuzz: 9599, 9600

Description:

Both issues are due to ERROR: libFuzzer: out-of-memory because of the usage of a large integer in the corpus. Added max constraint validate rule to the appropriate field.

Risk Level: Low

Testing: Tested unit tests (bazel test //test/server:server_fuzz_test and bazel test //test/server/config_validation:config_fuzz_test), built and ran fuzzers with oss-fuzz.

Signed-off-by: Anirudh M m.anirudh18@gmail.com

Signed-off-by: Anirudh M <m.anirudh18@gmail.com>
//
// Priorities should range from 0 (highest) to N (lowest) without skipping.
uint32 priority = 5;
uint32 priority = 5 [(validate.rules).uint32 = {gte: 0, lte: 128}];
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this looks basically right. You don't need the gte: 0 though, since this is an unsigned int. @alyssawilk what do you think a sensible upper bound here is? Will 128 work? Seems reasonable to me.

Signed-off-by: Anirudh M <m.anirudh18@gmail.com>
@mattklein123 mattklein123 merged commit eb5ea98 into envoyproxy:master Jul 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants