5984,6984 - Pentesting CouchDB
Last updated
Last updated
Learn & practice AWS Hacking: Learn & practice GCP Hacking:
CouchDB is a versatile and powerful document-oriented database that organizes data using a key-value map structure within each document. Fields within the document can be represented as key/value pairs, lists, or maps, providing flexibility in data storage and retrieval.
Every document stored in CouchDB is assigned a unique identifier (_id) at the document level. Additionally, each modification made and saved to the database is assigned a revision number (_rev). This revision number allows for efficient tracking and management of changes, facilitating easy retrieval and synchronization of data within the database.
Default port: 5984(http), 6984(https)
This issues a GET request to installed CouchDB instance. The reply should look something like on of the following:
/_active_tasks List of running tasks, including the task type, name, status and process ID.
/_all_dbs Returns a list of all the databases in the CouchDB instance.
**/_cluster_setup**Returns the status of the node or cluster, per the cluster setup wizard.
/_db_updates Returns a list of all database events in the CouchDB instance. The existence of the _global_changes database is required to use this endpoint.
/_membership Displays the nodes that are part of the cluster as cluster_nodes. The field all_nodes displays all nodes this node knows about, including the ones that are part of the cluster.
/_scheduler/jobs List of replication jobs. Each job description will include source and target information, replication id, a history of recent event, and a few other things.
/_scheduler/docs List of replication document states. Includes information about all the documents, even in completed and failed states. For each document it returns the document ID, the database, the replication ID, source and target, and other information.
/_scheduler/docs/{replicator_db}
/_scheduler/docs/{replicator_db}/{docid}
/_node/{node-name} The /_node/{node-name} endpoint can be used to confirm the Erlang node name of the server that processes the request. This is most useful when accessing /_node/_local to retrieve this information.
/_node/{node-name}/_stats The _stats resource returns a JSON object containing the statistics for the running server. The literal string _local serves as an alias for the local node name, so for all stats URLs, {node-name} may be replaced with _local, to interact with the local node’s statistics.
/_node/{node-name}/_system The _systemresource returns a JSON object containing various system-level statistics for the running server_._ You can use ___local as {node-name} to get current node info.
/_node/{node-name}/_restart
**/_uuids**Requests one or more Universally Unique Identifiers (UUIDs) from the CouchDB instance.
**/_reshard**Returns a count of completed, failed, running, stopped, and total jobs along with the state of resharding on the cluster.
If that request responds with a 401 unauthorised, then you need some valid credentials to access the database:
This is an example of a couchdb response when you have enough privileges to list databases (It's just a list of dbs):
You can obtain some database info (like number of files and sizes) accessing the database name:
List each entry inside a database
Read the content of a document inside a database:
Thanks to the differences between Erlang and JavaScript JSON parsers you could create an admin user with credentials hacktricks:hacktricks with the following request:
A crucial security advisory is highlighted regarding port 4369. If this port is made accessible over the Internet or any untrusted network, the system's security heavily relies on a unique identifier known as the "cookie." This cookie acts as a safeguard. For instance, in a given process list, the cookie named "monster" might be observed, indicating its operational role in the system's security framework.
A recently disclosed vulnerability, CVE-2018-8007, affecting Apache CouchDB was explored, revealing that exploitation requires write permissions to the local.ini file. Although not directly applicable to the initial target system due to security restrictions, modifications were made to grant write access to the local.ini file for exploration purposes. Detailed steps and code examples are provided below, demonstrating the process.
First, the environment is prepared by ensuring the local.ini file is writable, verified by listing the permissions:
To exploit the vulnerability, a curl command is executed, targeting the cors/origins configuration in local.ini. This injects a new origin along with additional commands under the [os_daemons] section, aiming to execute arbitrary code:
Subsequent verification shows the injected configuration in local.ini, contrasting it with a backup to highlight the changes:
Initially, the expected file (/tmp/0xdf) does not exist, indicating that the injected command has not been executed yet. Further investigation reveals that processes related to CouchDB are running, including one that could potentially execute the injected command:
By terminating the identified CouchDB process and allowing the system to automatically restart it, the execution of the injected command is triggered, confirmed by the existence of the previously missing file:
This exploration confirms the viability of CVE-2018-8007 exploitation under specific conditions, notably the requirement for writable access to the local.ini file. The provided code examples and procedural steps offer a clear guide for replicating the exploit in a controlled environment.
A vulnerability known as CVE-2017-12636 was explored, which enables code execution via the CouchDB process, although specific configurations may prevent its exploitation. Despite numerous Proof of Concept (POC) references available online, adjustments are necessary to exploit the vulnerability on CouchDB version 2, differing from the commonly targeted version 1.x. The initial steps involve verifying the CouchDB version and confirming the absence of the expected query servers path:
To accommodate CouchDB version 2.0, a new path is utilized:
Attempts to add and invoke a new query server were met with permission-related errors, as indicated by the following output:
Further investigation revealed permission issues with the local.ini file, which was not writable. By modifying the file permissions with root or homer access, it became possible to proceed:
Subsequent attempts to add the query server succeeded, as demonstrated by the lack of error messages in the response. The successful modification of the local.ini file was confirmed through file comparison:
The process continued with the creation of a database and a document, followed by an attempt to execute code via a custom view mapping to the newly added query server:
port:5984 couchdb
These are the endpoints where you can access with a GET request and extract some interesting info. You can find .
/_up Confirms that the server is up, running, and ready to respond to requests. If is true or nolb, the endpoint will return a 404 response.
More interesting information can be extracted as explained here:
In order to find valid Credentials you could try to .
.
Example .
In the CouchDB documentation, specifically in the section concerning cluster set-up (), the use of ports by CouchDB in a cluster mode is discussed. It's mentioned that, as in standalone mode, port 5984 is used. Additionally, port 5986 is for node-local APIs, and importantly, Erlang requires TCP port 4369 for the Erlang Port Mapper Daemon (EPMD), facilitating node communication within an Erlang cluster. This setup forms a network where each node is interlinked with every other node.
For those interested in understanding how this "cookie" can be exploited for Remote Code Execution (RCE) within the context of Erlang systems, a dedicated section is available for further reading. It details the methodologies for leveraging Erlang cookies in unauthorized manners to achieve control over systems. You can .
Example .
For more details on CVE-2018-8007, refer to the advisory by mdsec: .
Example .
A with an alternative payload provides further insights into exploiting CVE-2017-12636 under specific conditions. Useful resources for exploiting this vulnerability include:
Learn & practice AWS Hacking: Learn & practice GCP Hacking:
Check the !
Join the 💬 or the or follow us on Twitter 🐦 .
Share hacking tricks by submitting PRs to the and github repos.
