Missing double-slashes on Zyxel 2nd references #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
todb
changed the title
|
Thank you for reaching out. We noticed this as well yesterday right after the KEV was updated. We've updated the main site, and synced the changes to this repo. -Chris |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Expected behavior
Links should render normally when parsing the JSON in some HTML-like reader.
Observed behavior
Typo on the second link in the two Zyxel entries. missing the double slashes. Namely,
https:/should behttps://Testability
Read it with your eyeballs, or in an HTML-aware JSON parser for the vuln data. Namely, the entries for CVE-2024-40890 and CVE-2024-40891.