Page MenuHomeFreeBSD

CTF: Fix an out-of-bounds read
ClosedPublic

Authored by domagoj.stolfa_gmail.com on Mar 26 2021, 7:18 PM.
Tags
Referenced Files
Unknown Object (File)
Mon, Nov 4, 12:31 PM
Unknown Object (File)
Mon, Nov 4, 12:11 PM
Unknown Object (File)
Sep 26 2024, 10:40 AM
Unknown Object (File)
Sep 26 2024, 2:17 AM
Unknown Object (File)
Sep 15 2024, 5:34 PM
Unknown Object (File)
Sep 7 2024, 10:19 AM
Unknown Object (File)
Sep 4 2024, 7:13 PM
Unknown Object (File)
Sep 3 2024, 5:03 PM
Subscribers
None

Details

Summary

When prefixes such as struct, union, etc. are compared with the current type (e.g. struct foo), a comparison is made with the prefix. The code currently assumes that every type is a valid C type with a prefix, however at times, garbage ends up in this function causing an unpredictable crash with DTrace due to the isspace(*p) call or subsequent calls. An example that I've seen of this is the letter 's' being passed in, comparing true with struct as the comparison size was (q - p) == 1, but then we increment p with the length of "struct", resulting in an out of bounds read. This diff simply adds some robustness checks to the surrounding code to prevent this from happening and causing weird behaviour.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Thanks, this looks right to me.

This revision is now accepted and ready to land.Mar 27 2021, 2:50 PM

(Please let me know if you'd like me to commit this.)

(Please let me know if you'd like me to commit this.)

I think this is fine to commit -- I've been running it and ran into no issues. Thanks!

cddl/contrib/opensolaris/common/ctf/ctf_lookup.c
94

Sorry, I had been focusing on the other change. Could you explain why this part is needed? I'm having trouble seeing how q or p can end up being NULL.

This revision now requires review to proceed.Mar 27 2021, 6:01 PM
This revision is now accepted and ready to land.Mar 27 2021, 6:02 PM
cddl/contrib/opensolaris/common/ctf/ctf_lookup.c
94

Sorry, I had been focusing on the other change. Could you explain why this part is needed? I'm having trouble seeing how q or p can end up being NULL.

94

You're right. I've updated the diff to reflect it. I think it was left over from debugging when I thought my code had caused a memory corruption :-).