$ ./dconfig fetch Error: 401 Unauthorized But maybe the server accepts any non-empty token:
value: .Env.SECRET You might be able to read system files or environment variables of the dconfig process itself. The apply command might write to protected files (e.g., /etc/profile.d/ , .bashrc , or systemd units). If you control the remote config, you can inject malicious commands. dconfig 2
$ export DCONFIG_TOKEN=test $ ./dconfig fetch dconfig 2
$ ls -la -rw-r--r-- 1 user user 124 .dconfig.yaml -rwxr-xr-x 1 user user 2.1M dconfig Sample config: dconfig 2
$ env | grep DCONFIG (empty) Try fetching config without a token:
Flag obtained. If dconfig supports variable substitution in values, test with: