CVE-2019-20054 and CVE-2014-9730 #154
Open
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
GiessC
reviewed
Nov 8, 2023
GiessC
reviewed
Nov 8, 2023
GiessC
reviewed
Nov 8, 2023
GiessC
reviewed
Nov 8, 2023
GiessC
reviewed
Nov 8, 2023
|
3 upvotes for CVE-2019-20054 |
nickc5802
reviewed
Nov 8, 2023
nickc5802
reviewed
Nov 8, 2023
nickc5802
reviewed
Nov 8, 2023
|
2 upvotes for CVE-2014-9730 |
Co-authored-by: Nick Campbell <[email protected]>
jc7305
reviewed
Nov 9, 2023
| crash. UDF is just a type of file system called Universal Disk Format. Using | ||
| the correct image an attacker could force the kernel to read passed the buffer | ||
| when traversing the symlink causing a crash. This vulnerability is actually a | ||
| related vulnerabiltity to this original issue. This vulnerability is speicifically |
There was a problem hiding this comment.
You misspelled specifically on this line.
| name: | ||
| note: | ||
| name: "fs" | ||
| note: "fix is specifically in the fs directory and has to do with handling |
There was a problem hiding this comment.
You should capitalize Fix to make it consistent with the rest of your document.
| note: | ||
| answer: false | ||
| note: | | ||
| vulnerability has to do with symlinks and file systems images, no i18n |
There was a problem hiding this comment.
Same capitalization mistake here. Capitalize Vulnerability.
| discussed_as_security: false | ||
| any_discussion: true | ||
| note: | | ||
| Prasad J Pandit seems to have include three fix commits in a message to |
| stacktrace_with_fix: false | ||
| note: | | ||
| There does not seem to be a stack trace anywhere. Since this required a | ||
| corrupted file system image, its possible the root of the problem could |
| CWE_note: "Manually confirmed" | ||
| mistakes: | ||
| answer: | | ||
| This seems to be a lapse in planning the error handling. The reset |
| This seems to be a lapse in planning the error handling. The reset | ||
| of the code assumes the parent pointer to not be null, since a properly | ||
| setup sub directory will have a parent directory pointer. This is fair to | ||
| assume sine the setup of the parent node is done at the beginning. However |
|
2 upvotes for CVE-2019-20054 |
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.
Linux Kernel Vulnerability History Project contribution