-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Rethrow NoSuchFileException if encountering an invalid symlink when checking file entitlements #124483
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
Merged
elasticsearchmachine
merged 6 commits into
elastic:main
from
mosche:entitlements/NoSuchFileExceptionForInvalidLinks
Mar 11, 2025
Merged
Rethrow NoSuchFileException if encountering an invalid symlink when checking file entitlements #124483
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
4c1877b
Rethrow NoSuchFileException if encountering an invalid symlink when c…
mosche f0c2718
Allow EntitlementsDeniedNonModularIT
mosche 24eb812
Merge branch 'main' into entitlements/NoSuchFileExceptionForInvalidLinks
prdoyle c7b4cda
Merge branch 'main' into entitlements/NoSuchFileExceptionForInvalidLinks
mosche 00a09bd
feedback
mosche 5089e18
feedback
mosche File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -35,6 +35,7 @@ | |
| import java.lang.StackWalker.StackFrame; | ||
| import java.lang.module.ModuleFinder; | ||
| import java.lang.module.ModuleReference; | ||
| import java.nio.file.NoSuchFileException; | ||
| import java.nio.file.Path; | ||
| import java.nio.file.Paths; | ||
| import java.util.ArrayList; | ||
|
|
@@ -326,10 +327,17 @@ private static boolean isPathOnDefaultFilesystem(Path path) { | |
| } | ||
|
|
||
| public void checkFileRead(Class<?> callerClass, Path path) { | ||
| checkFileRead(callerClass, path, false); | ||
| try { | ||
| checkFileRead(callerClass, path, false); | ||
| } catch (NoSuchFileException e) { | ||
| assert false : "NoSuchFileException should only be thrown when following links"; | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this is the right approach for where we are now; if we go forward with the idea of moving towards exceptions already in the method contract (e.g. IOExceptions for File operations) we will revisit this with all the other methods |
||
| var notEntitledException = new NotEntitledException(e.getMessage()); | ||
| notEntitledException.addSuppressed(e); | ||
| throw notEntitledException; | ||
| } | ||
| } | ||
|
|
||
| public void checkFileRead(Class<?> callerClass, Path path, boolean followLinks) { | ||
| public void checkFileRead(Class<?> callerClass, Path path, boolean followLinks) throws NoSuchFileException { | ||
| if (isPathOnDefaultFilesystem(path) == false) { | ||
| return; | ||
| } | ||
|
|
@@ -345,11 +353,13 @@ public void checkFileRead(Class<?> callerClass, Path path, boolean followLinks) | |
| if (canRead && followLinks) { | ||
| try { | ||
| realPath = path.toRealPath(); | ||
| if (realPath.equals(path) == false) { | ||
| canRead = entitlements.fileAccess().canRead(realPath); | ||
| } | ||
| } catch (NoSuchFileException e) { | ||
| throw e; // rethrow | ||
| } catch (IOException e) { | ||
| // target not found or other IO error | ||
| } | ||
| if (realPath != null && realPath.equals(path) == false) { | ||
| canRead = entitlements.fileAccess().canRead(realPath); | ||
| canRead = false; | ||
| } | ||
| } | ||
|
|
||
|
|
||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly for future work: should we add a check that we match the target method's checked exceptions? We would not like to use an incorrect exception type by mistake, it might end up with another "VerifyError"-style problem again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC the
throwsclause doesn't affect bytecode, so it can't cause a verification error. It's only there for javac.