You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the fuzzing driver code (shown below), the file /dev/null is opened in "r" (read) mode which is typically used for reading input. However, the common practice when directing output to /dev/null, especially in testing or logging scenarios, is to open it in "w" (write) mode. This issue can potentially lead to misunderstandings or misuse of file handling in the driver.
If my understanding is correct, this line should be modified to open /dev/null in "w" mode to adhere to its intended use as an output discard mechanism.
Looking forward to your kind reply or explanation. Thanks in advance. :)
The text was updated successfully, but these errors were encountered:
Describe the bug
In the fuzzing driver code (shown below), the file
/dev/null
is opened in "r" (read) mode which is typically used for reading input. However, the common practice when directing output to/dev/null
, especially in testing or logging scenarios, is to open it in "w" (write) mode. This issue can potentially lead to misunderstandings or misuse of file handling in the driver.libcbor/oss-fuzz/cbor_load_fuzzer.cc
Line 64 in a0582ab
Expected behavior
If my understanding is correct, this line should be modified to open /dev/null in "w" mode to adhere to its intended use as an output discard mechanism.
Looking forward to your kind reply or explanation. Thanks in advance. :)
The text was updated successfully, but these errors were encountered: