Approved changes feed: RSS · Atom

cpe:2.3:a:apache:couchdb:3.0.0:*:*:*:*:*:*:*

part: a version: 3.0.0 update: *

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductCouchdb (3de04e4d-acf5-50dd-b2a1-80e025817e6a)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:apache/couchdb purl2cpe 2026-06-01 10:14:25.191747
pkg:docker/couchdb purl2cpe 2026-06-01 10:14:25.191748
pkg:github/apache/couchdb purl2cpe 2026-06-01 10:14:25.191750
pkg:gitlab/kalilinux/couchdb purl2cpe 2026-06-01 10:14:25.191751
pkg:rpm/fedora/couchdb purl2cpe 2026-06-01 10:14:25.191752
pkg:rpm/opensuse/couchdb purl2cpe 2026-06-01 10:14:25.191754

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2020-1955 vulnerable 2026-06-08 05:21:03.757333 Details available
CouchDB version 3.0.0 shipped with a new configuration setting that governs access control to the entire database server called `require_valid_user_except_for_up`. It was meant as an extension to the long standing setting `require_valid_user`, which in turn requires that any and all requests to CouchDB will have to be made with valid credentials, effectively forbidding any anonymous requests. The new `require_valid_user_except_for_up` is an off-by-default setting that was meant to allow requiring valid credentials for all endpoints except for the `/_up` endpoint. However, the implementation of this made an error that lead to not enforcing credentials on any endpoint, when enabled. CouchDB versions 3.0.1[1] and 3.1.0[2] fix this issue.
Published: 2020-05-20T13:53:44.000Z
Updated: 2024-08-04T06:54:00.400Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.