Malformed mach object can cause OOM when parsed

[5225225]

This is seems to be inside goblin. (Which is weird, I thought that crate was well fuzzed?)

fn main() {
    let data = b"\xfe\xed\xfa\xce\xce\xfa\xff\xfe\xcf*\x06;\xfe\xfa\xce\xff\xff\xff\xff0\xce:\xfa\xffj\xfe\xcf*\x06\x00;\xc6";
    symbolic::debuginfo::macho::MachObject::parse(data);
}

==511870==ERROR: AddressSanitizer: requested allocation size 0x137ffff0280 (0x137ffff1280 after adjustments for alignment, red zones etc.) exceeds maximum supported size of 0x10000000000 (thread T0)
    #0 0x55935ca6c49d in malloc /rustc/llvm/src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:129:3
    #1 0x55935e09f7de in goblin::mach::MachO::parse::h2911619bbe3c6e71 (/home/jess/.cache/cargo/target/x86_64-unknown-linux-gnu/release/mach+0x269e7de)
    #2 0x55935cd9e0cf in symbolic_debuginfo::macho::MachObject::parse::he7798c7c3eea637c (/home/jess/.cache/cargo/target/x86_64-unknown-linux-gnu/release/mach+0x139d0cf)
    #3 0x55935caa0f24 in rust_fuzzer_test_input (/home/jess/.cache/cargo/target/x86_64-unknown-linux-gnu/release/mach+0x109ff24)
    #4 0x55935e69d9a8 in __rust_try libfuzzer_sys.028fe43b-cgu.0
    #5 0x55935e6996bd in LLVMFuzzerTestOneInput (/home/jess/.cache/cargo/target/x86_64-unknown-linux-gnu/release/mach+0x2c986bd)
    #6 0x55935e6b2901 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) (/home/jess/.cache/cargo/target/x86_64-unknown-linux-gnu/release/mach+0x2cb1901)
    #7 0x55935e6a683a in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) (/home/jess/.cache/cargo/target/x86_64-unknown-linux-gnu/release/mach+0x2ca583a)
    #8 0x55935e6aa852 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) (/home/jess/.cache/cargo/target/x86_64-unknown-linux-gnu/release/mach+0x2ca9852)
    #9 0x55935c9efd42 in main (/home/jess/.cache/cargo/target/x86_64-unknown-linux-gnu/release/mach+0xfeed42)
    #10 0x7fca96b13b24 in __libc_start_main (/usr/lib/libc.so.6+0x27b24)

[Swatinem]

I created m4b/goblin#298 with a fix for this.

Big thanks @5225225 ❤️ this is awesome work!