Port 5984 · CouchDB

All network ports
Databases & caches · Registered5984/tcp

Port / TCP

5984CouchDB

CouchDB's HTTP API for documents, views, and replication.

If it is internet-facing: Finding 5984 open to the internet is a finding in its own right — it warrants an explanation, not just a rule.

Exposure

Trusted network only

Transport

Encryption optional

Risk if public

High

Exposure verdict

ReachTrusted network only

Port 5984 belongs on a trusted internal network. If a perimeter scan finds it answering, treat that as a firewall defect rather than a configuration preference.

TransportEncryption optional

Encryption is available but negotiated or configured rather than guaranteed. A client that does not insist on it will silently fall back to plaintext.

RangeRegistered (1024–49151)

Registered with IANA on request, but bindable by any unprivileged user. Registration records intent — it does not reserve the port, so collisions between products are common.

FamilyDatabases & caches

Grouped with the other databases & caches ports so a rule written for one can be checked against its neighbours.

What actually goes wrong

2 notes
  • Versions before 3.0 started in 'admin party' mode where every request had administrative rights.
  • The HTTP interface means a single unauthenticated request can dump or delete a database.

Recommended firewall rule

Allow only from 10.0.0.0/8, drop the rest

Swap in the CIDR your administrators or application tier actually come from — the point is that the default answer is no.

ufw

sudo ufw allow from 10.0.0.0/8 to any port 5984 proto tcp

iptables

sudo iptables -A INPUT -p tcp -s 10.0.0.0/8 --dport 5984 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 5984 -j DROP

If you do need it open to everyone

sudo ufw allow 5984/tcp

Write down why. An unexplained allow rule outlives the person who added it, and the next reviewer has no way to tell a deliberate exception from an accident.

Check what is really there

Listening locally

sudo ss -tlpn 'sport = :5984'

The bind address is the answer that matters: 127.0.0.1 is local-only, 0.0.0.0 and :: mean every interface.

Listening (macOS)

sudo lsof -nP -iTCP:5984 -sTCP:LISTEN

macOS ships lsof rather than ss; this names the owning process and user.

From outside

nmap -sV -Pn -p 5984 <host>

A version probe confirms whether CouchDB is actually what answers, rather than trusting the number. Only scan hosts you are authorised to test.

Reachability

nc -vz <host> 5984

The quick yes/no when you only need to know whether a path exists through the firewall.

Nearby and related ports

8
ProtocolTCP
Rangeregistered
Transportopportunistic
Exposureprivate