-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault when if-feature is used in list key node, with a non existing feature #723
Comments
Hi, Regards, |
CVE-2019-20392 was assigned to this issue. |
@ret2libc |
@SuhwanSong Yesterday. Is it ok? |
@ret2libc Thanks! I requested CVEs but I've not received any reply except confirm email. |
No it generally takes one or two days at most. Did you request CVEs for any of these issues that already for a CVE? Did you request them to MITRE? |
@ret2libc Besides these issues that I've reported are not assigned as CVE. But I got no replies from them, so there are still many issues that I haven't reported yet such as |
If an if-feature statement is used inside a list key node, and the feature used is not defined, yanglint and yangfuzz segfault in lys_parse_path.
Here is an example of a yang file that crashes the parser:
The text was updated successfully, but these errors were encountered: