[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

How to handle undetermined



Hi

I got some time over in my triaging so I thought I should check some of the undetermined issues. There may be lurking some problematic things there.

What I did was to check CVE-2016-10729 and my conclusion that I cannot reproduce the problem.
It may be so that the checks are not in place but there are obviously something preventing the exploit to be reproducible. Either that or that you have to be logged in as backup, which is not possible.

My question to you is how to properly mark this vulnerability. Is it so that it should be "undetermined" or should I mark it in some other way?

Best regards

// Ola



--
 --- Inguza Technology AB --- MSc in Information Technology ----
/  ola@inguza.com                    Folkebogatan 26            \
|  opal@debian.org                   654 68 KARLSTAD            |
|  http://inguza.com/                Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---------------------------------------------------------------


Reply to: