cstamas commented on code in PR #2079:
URL: https://github.com/apache/maven-resolver/pull/2079#discussion_r3892610712
##########
maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/synccontext/named/BasedirNameMapper.java:
##########
@@ -93,11 +93,26 @@ public Collection<NamedLockKey> nameLocks(
: DirectoryUtils.resolveDirectory(session,
DEFAULT_LOCKS_DIR, CONFIG_PROP_LOCKS_DIR, false);
return delegate.nameLocks(session, artifacts, metadatas).stream()
- .map(k -> NamedLockKey.of(
-
basedir.resolve(k.name()).toAbsolutePath().toUri().toASCIIString(),
k.resources()))
+ .map(k -> NamedLockKey.of(resolveContained(basedir,
k.name()), k.resources()))
.collect(Collectors.toList());
} catch (IOException e) {
throw new UncheckedIOException(e);
}
}
+
+ /**
+ * Resolves the delegate-provided lock name against the locks base
directory, rejecting any name that would
+ * escape it. Lock names are derived from artifact coordinates that arrive
from remote repositories; a name
+ * containing path traversal must never select a lock file outside the
locks directory, as locks are created
+ * (and deleted on close) by the file lock factory at the resolved path.
+ *
+ * @since 2.0.22
+ */
+ private static String resolveContained(Path basedir, String name) {
+ Path resolved = basedir.resolve(name).toAbsolutePath();
+ if
(!resolved.normalize().startsWith(basedir.toAbsolutePath().normalize())) {
Review Comment:
Again, doing this for each lock... `basedir` should be treated like this in
ctor?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
