Vivin Paliath

Heap buffer overflow (read) in DnsResource::getDataLength() at DnsResource.cpp:277:24

3

There is a buffer overflow at the specified location: ``` ==4123050==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x607000005a93 at pc 0x000000681f70 bp 0x7ffcb25feaa0 sp 0x7ffcb25fea98 READ of size 2 at 0x607000005a93 thread...

Heap buffer overflow (read) in IgmpLayer::getIGMPVerFromData(unsigned char*, unsigned long, bool&) at IgmpLayer.cpp:81:7

2

There is a buffer overflow at the specified location: ``` ==854686==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60400000f2b7 at pc 0x000000761fc0 bp 0x7fffe21bf0e0 sp 0x7fffe21bf0d8 READ of size 1 at 0x60400000f2b7 thread...

Heap buffer overflow (read) in RadiusLayer::isDataValid(unsigned char const*, unsigned long) at RadiusLayer.cpp:246:19

2

There is a buffer overflow at the specified location: ``` ==902091==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x606000000420 at pc 0x0000005c944c bp 0x7fff0bdc72c0 sp 0x7fff0bdc72b8 READ of size 2 at 0x606000000420 thread...

OverflowError: cannot fit 'int' into an index-sized integer while using CFGEmulated with keep_state=True

5

I'm trying to create a CFG on the babyheap binary located [here](https://github.com/guyinatuxedo/ctf/tree/master/0ctf/pwn/babyheap). When I have `keep_state=True`, I get the following stacktrace: ``` Traceback (most recent call last): File "babyheap_analysis.py", line...

Generating embeddings

1

Sorry if this is a dumb question, but does this also generate word embeddings?

I am trying to perform parallel fuzzing with the main instance fuzzing a binary with regular instrumentation, and the child instances fuzzing a binary with custom instrumentation. But this fails...

There is a 1-byte read overflow in `convert_char4` in `dmg2img.h`: ``` ================================================================= ==1504730==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf49007c8 at pc 0x08112bf5 bp 0xffced768 sp 0xffced760 READ of size 1 at...

In addition to the `MDY`, `YMD`, and `DMY` formats, we'll have to support "wire format" as well. This way `@Past` and `@Future` could be used with `date`, `time`, and `datetime`...

[Section 4.3](http://json-schema.org/latest/json-schema-hypermedia.html#anchor10) of the JSON Schema specification mentions the `media` property, which is used to give additional hints about the semantics of non-JSON data that is encoded as a JSON...