Text of codeql.github.com › codeql-query-help › java › java-relative-path-command as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

Executing a command with a relative path — CodeQL query help documentation

CodeQL query help documentation » CodeQL query help for Java and Kotlin » Executing a command with a relative path ¶ ID: java/relative-path-command Kind: problem Security severity: 5.4 Severity: warning Precision: medium Tags: - security - external/cwe/cwe-078 - external/cwe/cwe-088 Query suites: - java-security-extended.qls - java-security-and-quality.qls Click to see the query in the CodeQL repository When a command is executed with a relative path, the runtime uses the PATH environment variable to find which executable to run.

Therefore, any user who can change the PATH environment variable can cause the software to run a different, malicious executable. Recommendation ¶ In most cases, simply use a command that has an absolute path instead of a relative path. In some cases, the location of the executable might be different on different installations. In such cases, consider specifying the location of key executables with some form of configuration.

When using this approach, be careful that the configuration system is not itself vulnerable to malicious modifications. Example ¶ class Test { public static void main ( String [] args ) { // BAD: relative path Runtime . getRuntime (). exec ( "make" ); // GOOD: absolute path Runtime . getRuntime (). exec ( "/usr/bin/make" ); // GOOD: build an absolute path from known values Runtime . getRuntime (). exec ( Paths . MAKE_PREFIX + "/bin/make" ); } } References ¶ Common Weakness Enumeration: CWE-78 .

Common Weakness Enumeration: CWE-88 . © GitHub, Inc. Terms Privacy