CouchdbApplication · Apache

CVE-2010-2234

MEDIUM · 6.8 CVSS v2.0 Published 2010-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-site request forgery (CSRF) vulnerability in Apache CouchDB 0.8.0 through 0.11.0 allows remote attackers to hijack the authentication of administrators for direct requests to an installation URL.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CSRF vulnerability in Apache CouchDB 0.8.0-0.11.0 allows remote attackers to hijack administrator authentication by tricking admins into making direct requests to the installation URL, enabling unauthorized administrative actions.

MitigationUpgrade CouchDB to version 0.11.1 or later which includes CSRF protections, or implement anti-CSRF tokens on all administrative interface forms and endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CouchdbApplication
Affected:= 0.8.0= 0.8.1= 0.9.0= 0.9.1= 0.9.2= 0.10.0= 0.10.1= 0.11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Apache CouchDB is installed
    Check for CouchDB processes running on the system (e.g., 'ps aux | grep couch' on Linux, or check services on Windows). Also look for CouchDB directories such as /var/lib/couchdb, /opt/couchdb, or C:\CouchDB.
    Affected if CouchDB is not running or not installed on the system.
  2. Determine the installed CouchDB version
    Make an HTTP request to the CouchDB server's welcome endpoint: GET http://localhost:5984/ or the configured host. Check the 'version' field in the JSON response.
    Affected if The returned version is one of: 0.8.0, 0.8.1, 0.9.0, 0.9.1, 0.9.2, 0.10.0, 0.10.1, or 0.11.0.
  3. Verify the administrative interface is accessible
    Check if the CouchDB administrative interface (Futon) is accessible by accessing http://localhost:5984/_utils/ or the equivalent path on your configured host. Confirm the /_config endpoint responds to administrative requests.
    Affected if The administrative interface is exposed and reachable over the network without restrictions.

You are affected if CouchDB version 0.8.0 through 0.11.0 is installed and its administrative interface is accessible, since these versions lack CSRF protection for admin actions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CouchDB to version 0.11.1 or later which includes CSRF protections, or implement anti-CSRF tokens on all administrative interface forms and endpoints.

Fix this in Couchdb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-2234 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-2234 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data