Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSS-Fuzz: Stack-overflow in XML_Node::RemoveContent #1877

Closed
kevinbackhouse opened this issue Aug 20, 2021 · 0 comments · Fixed by #1878 or #1880
Closed

OSS-Fuzz: Stack-overflow in XML_Node::RemoveContent #1877

kevinbackhouse opened this issue Aug 20, 2021 · 0 comments · Fixed by #1878 or #1880
Assignees
Labels
bug OSS-Fuzz Bug reported by https://google.github.io/oss-fuzz/
Milestone

Comments

@kevinbackhouse
Copy link
Collaborator

We got our first bug report from OSS-Fuzz.

To nobody's surprise, it's a bug in xmpsdk. I have to admit that I was already aware of this issue, but had attempted to sweep it under the carpet by limiting the size of the images in the corpus to at most 20KB. The bug is triggered by a deeply nested XML tree, which causes a stack overflow in xmpsdk's recursive code. It's worth noting that the maximum stack size is much more limited in the fuzzer than in the normal exiv2 application, so the attached poc does not crash exiv2. However, a sufficiently large poc could crash exiv2.

poc: clusterfuzz-testcase-minimized-fuzz-read-print-write-5342978104229888.tar.gz

@kevinbackhouse kevinbackhouse self-assigned this Aug 20, 2021
@kevinbackhouse kevinbackhouse added bug OSS-Fuzz Bug reported by https://google.github.io/oss-fuzz/ labels Aug 27, 2021
This was referenced Sep 8, 2021
@kevinbackhouse kevinbackhouse modified the milestones: v1.00, v0.27.5 Dec 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug OSS-Fuzz Bug reported by https://google.github.io/oss-fuzz/
Projects
None yet
1 participant