Dconfig 2 -

"DB_PASSWORD": "flag...", "API_KEY": "secret123"

$ ./dconfig fetch Error: 401 Unauthorized But maybe the server accepts any non-empty token:

Flag obtained. If dconfig supports variable substitution in values, test with:

Example payload in remote config:

$ file dconfig dconfig: ELF 64-bit executable $ ./dconfig --help Usage: dconfig [OPTIONS] COMMAND Commands: fetch Retrieve config from remote source apply Apply config to local environment validate Check config syntax

bash"

Look for configuration files or environment hints: dconfig 2

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.

After ./dconfig apply , the system runs the attacker’s script. flagdconfig_2_config_injection_success

$ env | grep DCONFIG (empty) Try fetching config without a token: "DB_PASSWORD": "flag

If you meant a different context (e.g., a specific challenge named “dconfig 2” from a CTF), please clarify. Overview dconfig 2 is a configuration management utility or challenge focused on handling distributed application settings, environment overrides, and secret injection. In many CTF challenges, dconfig refers to a tool that pulls configs from a remote source (e.g., etcd, Consul, or a custom HTTP endpoint) and applies them locally.

Here’s a write-up for , structured as a technical or security write-up (depending on the context—CTF, tool usage, or system configuration).

$ export DCONFIG_TOKEN=test $ ./dconfig fetch If you control the remote config, you can