CVE-2020-1955
published 2020-05-20CVE-2020-1955: CouchDB version 3.0.0 shipped with a new configuration setting that governs access control to the entire database server called…
PriorityP357critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
1.85%
76.6th percentile
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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apache | couchdb | — | — |
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Cross-site Scripting vulnerability in Jenkins
ghsa·2022-06-24
CVE-2022-34170 [HIGH] CWE-22 Cross-site Scripting vulnerability in Jenkins
Cross-site Scripting vulnerability in Jenkins
Since Jenkins 2.320 and LTS 2.332.1, help icon tooltips no longer escape the feature name, effectively undoing the fix for [SECURITY-1955](https://www.jenkins.io/security/advisory/2020-08-12/#SECURITY-1955).
This vulnerability is known to be exploitable by attackers with Job/Configure permission.
Jenkins 2.356, LTS 2.332.4 and LTS 2.346.1 addresses this vulnerability, the feature name in help icon tooltips is now escaped.
GHSA
GHSA-6625-2573-pv96: CouchDB version 3
ghsa_unreviewed·2022-05-24
CVE-2020-1955 [MEDIUM] CWE-269 GHSA-6625-2573-pv96: CouchDB version 3
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-2229 jenkins: user-specified tooltip values leads to stored cross-site scripting
bugzilla·2020-09-02·CVSS 5.4
CVE-2020-2229 [MEDIUM] CVE-2020-2229 jenkins: user-specified tooltip values leads to stored cross-site scripting
CVE-2020-2229 jenkins: user-specified tooltip values leads to stored cross-site scripting
Jenkins 2.251 and earlier, LTS 2.235.3 and earlier does not escape the tooltip content of help icons. Tooltip values can be contributed by plugins, some of which use user-specified values. This results in a stored cross-site scripting (XSS) vulnerability.
Discussion:
Created jenkins tracking bugs for this issue:
Affects: fedora-31 [bug 1874831]
---
External References:
https://jenkins.io/security/advisory/2020-08-12/#SECURITY-1955
---
This issue has been addressed in the following products:
Red Hat OpenShift Container Platform 4.5
Via RHSA-2020:3841 https://access.redhat.com/errata/RHSA-2020:3841
---
This bug is now closed. Further updates for individual products will be reflected on the
Bugzilla
CVE-2020-1955 couchdb: remote privilege escalation when require_valid_user_except_for_up setting is enable [fedora-all]
bugzilla·2020-05-26·CVSS 9.8
CVE-2020-1955 [CRITICAL] CVE-2020-1955 couchdb: remote privilege escalation when require_valid_user_except_for_up setting is enable [fedora-all]
CVE-2020-1955 couchdb: remote privilege escalation when require_valid_user_except_for_up setting is enable [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this
Bugzilla
CVE-2020-1955 couchdb: remote privilege escalation when require_valid_user_except_for_up setting is enable
bugzilla·2020-05-26·CVSS 9.8
CVE-2020-1955 [CRITICAL] CVE-2020-1955 couchdb: remote privilege escalation when require_valid_user_except_for_up setting is enable
CVE-2020-1955 couchdb: remote privilege escalation when require_valid_user_except_for_up setting is enable
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. Co
2020-05-20
Published